-
Notifications
You must be signed in to change notification settings - Fork 62
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
Setting HOME env variable when unset due to downstream failures [JIRA: TOOLS-138] #185
Conversation
Silly shells. Would you mind using 'id -un' instead of whoami as I'm not sure whoami is IEEE1003.2/POSIX.2 (but don't have a copy of it handy to be sure). |
@jonmeredith looks like WHOAMI is used in a few spots. Are you thinking about comprehensive change, or just for the localized to the HOME var? |
POSIX.2 is reportedly very similar to the Single UNIX Specification, where it appears |
Haha, teach me to look at just the diff and put my foot in it. If we're using whoami in other places successfully on our platforms I'm less concerned. Ideally we'd standardize on SUS/POSIX.2 commands. |
Just curious, do we write to $HOME, anywhere in the code? |
@jonmeredith whoami has been used for quite some time in this script. I agree it should probably be changed to @sargun I wasn't able to find any other places writing to the HOME env variable in the release code for Riak anyway, nor did I find anything reading from it. I think |
create jira issue |
Can this be prioritized in the next set of DevOps work? _[posted via JIRA by Derek Somogyi]_ |
Review submitted PR [JIRA: TOOLS-138]
this is merged [where is the close ticket button?] _[posted via JIRA by David Andersen]_ |
Related issue here: basho/cuttlefish#193
"erlexec requires the HOME variable to be set.
The way that this manifests itself during normal Riak startups, if $HOME isn't set:
Can we automatically set $HOME, if it's not set already?"
I've addressed this with the following addition to
env.sh
: