Trans
5/20/2008 2:01:00 AM
On May 19, 3:46=A0pm, Gregory Seidman <gsslist+r...@anthropohedron.net>
wrote:
> On Tue, May 20, 2008 at 04:07:13AM +0900, Trans wrote:
> > My Ruby installation is from the Ubuntu package repository. Yesterday,
> > I upgraded my system to Heron and since then one of my Ruby scripts
> > stopped working. I traced the problem to this:
>
> > =A0 $ ruby -e"p ENV['ROLL_PATH']"
> > =A0 "/home/trans/Company/TigerOps/programs"
>
> > =A0 $ sudo ruby -e"p ENV['ROLL_PATH']"
> > =A0 nil
>
> > At first I though it might have something to do with sudo itself, but:
>
> Yes, it's sudo. Your test is flawed.
>
> > =A0 $ echo $ROLL_PATH
> > =A0 /home/trans/Company/TigerOps/programs
>
> > =A0 $ sudo echo $ROLL_PATH
> > =A0 /home/trans/Company/TigerOps/programs
>
> $ROLL_PATH is interpreted by the shell before sudo is ever invoked.
>
> > So that's not it. Anyone have any idea what's going on?
>
> [...]
>
> This is unrelated to Ruby or Ubuntu. This is how sudo works. Read the
> sudoers man page, looking for env_keep. You will need to edit the
> /etc/sudoers file (with visudo, not directly).
Ok. That makes sense. Though I don't yet understand what changed --it
was working fine before the dist-upgrade.
Thanks,
T.