Skip to content
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

Document env.sudo_prefix #564

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

Document env.sudo_prefix #564

bitprophet opened this issue Feb 18, 2012 · 3 comments

Comments

@bitprophet
Copy link
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".)

@ghost ghost assigned bitprophet Feb 18, 2012
@ScottSturdivant
Copy link

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"

@ScottSturdivant
Copy link

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
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants