Document env.sudo_prefix #564

Closed
bitprophet opened this Issue Feb 18, 2012 · 3 comments

Projects

None yet

2 participants

@bitprophet
Member

env.sudo_prefix works to specify which sudo is being called, which is an uncommon but not entirely rare need for users whose default $PATH does not include it.

However, it's not documented, and probably should be.

(Was: "Allow override of which sudo binary is used".)

@bitprophet bitprophet was assigned Feb 18, 2012
@SirScott

Thanks for working this, sorry for being an oddball...

The error I was seeing was:

out: bash: sudo: command not found

Fatal error: sudo() received nonzero return code 127 while executing!

Requested: /bin/mv /tmp/yum.conf /etc/yum.conf
Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "/bin/mv /tmp/yum.conf /etc/yum.conf"

@SirScott

Looks like I can modify this with env['sudo_prefix']. That's totally workable for me, so feel free to close this issue. Thanks again for your help thinking about this!

@bitprophet
Member

Yup, I'd forgotten about sudo_prefix and it works just fine to solve this issue. Thanks for sharing your resolution :)

That said, it appears to be undocumented and I cannot think of a good reason for this, so this issue is now about documenting it.

@bitprophet bitprophet added a commit that closed this issue Apr 6, 2012
@bitprophet bitprophet Clean up & document env.sudo_prefix.
Fixes #609, fixes #564
6bf1d90
@bitprophet bitprophet closed this in 6bf1d90 Apr 6, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment