Uh oh!
There was an error while loading. Please reload this page.
Setting HOME env variable when unset due to downstream failures [JIRA: TOOLS-138] - #185
Conversation
jonmeredith
commented
Jul 13, 2015
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). |
randysecrist
commented
Jul 13, 2015
@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? |
macintux
commented
Jul 13, 2015
POSIX.2 is reportedly very similar to the Single UNIX Specification, where it appears |
jonmeredith
commented
Jul 13, 2015
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. |
sargun
commented
Jul 13, 2015
Just curious, do we write to $HOME, anywhere in the code? |
drewkerrigan
commented
Jul 13, 2015
@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 |
DSomogyi
commented
Aug 7, 2015
create jira issue |
Basho-JIRA
commented
Aug 7, 2015
Can this be prioritized in the next set of DevOps work? _[posted via JIRA by Derek Somogyi]_ |
Review submitted PR [JIRA: TOOLS-138]
Basho-JIRA
commented
Sep 29, 2015
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: