We have a bunch of old debian sarge distros running and we're slowly
upgrading to Ubuntu Feisty Fawn.
For reasons that are not important here, we need to run our python app as
root. So we added
ALL ALL = NOPASSWD: /usr/bin/python
to the sudoers file. (Yeah yeah don't start.)
The problem
On Mon, Jul 21, 2008 at 2:07 PM, Steven W. Orr [EMAIL PROTECTED] wrote:
We have a bunch of old debian sarge distros running and we're slowly
upgrading to Ubuntu Feisty Fawn.
For reasons that are not important here, we need to run our python app as
root. So we added
ALL ALL = NOPASSWD:
On Monday, Jul 21st 2008 at 14:18 -, quoth Mark Greene:
=On Mon, Jul 21, 2008 at 2:07 PM, Steven W. Orr [EMAIL PROTECTED]
=wrote:
= We have a bunch of old debian sarge distros running and we're
= slowly
= upgrading to Ubuntu Feisty Fawn.
=
= For reasons that are not
On Mon, 2008-07-21 at 14:25 -0400, Shawn O'Shea wrote:
The problem is that under the FF release, sudo is acting
broken, i.e., not
like the man page sez it's supposed to. Under FF, I lose my
HOME envvar.
I'm not supposed to lose it.
The problem is that under the FF release, sudo is acting broken, i.e., not
like the man page sez it's supposed to. Under FF, I lose my HOME envvar.
I'm not supposed to lose it.
503 sudo python
Python 2.5.1 (r251:54863, Mar 7 2008, 04:10:12)
[GCC 4.1.3 20070929 (prerelease) (Ubuntu
On Monday, Jul 21st 2008 at 14:25 -, quoth Shawn O'Shea:
=
=
=
= The problem is that under the FF release, sudo is acting
= broken, i.e., not
= like the man page sez it's supposed to. Under FF, I lose my
= HOME envvar.
= I'm not supposed to lose it.
=
= 503 sudo
As a sanity check, I'd verify whether it's being removed by sudo
or by python:
ALL ALL = NOPASSWD: /bin/bash
sudo bash
echo $HOME
After verifying which was responsible, the next thing I'd wonder
is whether SELinux is doing something unexpected.
On Mon, July 21, 2008 2:07 pm,
