-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Env variables (i.e. WAIT_FOR_ERLANG) do not persist during startup. #563
Comments
This leaves us in a bit of a pickle, using 'service' strips all env, and Solaris doesn't support |
alternately /usr/sbin/riak could source /etc/default/riak. Feels like a bit of a hack though, not sure that's the behavior we want. |
That's what I was initially thinking. We source it from the init.d script, On Mon, Jun 23, 2014 at 2:17 PM, Jon Glick notifications@github.com wrote:
|
@jaredmorrow were there any fixes outside basho/node_package#146 needed to close this? |
Something needs to still happen, I just needed to come back to it. I'll take a look again at it tomorrow. |
Looks good, visual +1 |
Will close issue when it is confirmed fixed in the RC packages. |
Reproduce:
On Ubuntu (12.04), save 'export WAIT_FOR_ERLANG=60' in /etc/default/riak, run 'service riak start' which takes longer than 15 seconds. Notice it still only waits 15 seconds, not 60.
Variables set in /etc/default/riak don't persist if /usr/sbin/riak has to change the user riak is run as.
https://github.com/basho/node_package/blob/develop/priv/base/env.sh#L234
'su -' doesn't preserve env variables, should probably be 'su -m'.
The text was updated successfully, but these errors were encountered: