On Wed, Sep 14, 2005 at 05:45:08PM +0200, Holly Bostick wrote: > OK, you're right. I think that the problems that I was working around > may have been based in *sudo*, not su itself, which works fine (now), as > does sudo su. But when I was setting up my system with sudo (like a > month and a half ago), I had all kinds of issues, because sudo did not > seem to source anything (or at least not in the way I expected). For > example, I had some weird borked PATH (the default ENV_SUPATH as you > said above, rather than the root PATH, which I would expect from a sudo > su -) , programs opened as (sudo su) root were opening with user > colors and themes (though they worked with root privs), and that sort of > thing. It was really bizarre, so I had a bunch of bizarre workarounds to > get things to work as it seemed they should, but didn't.
right. sudo doesn't start a sub-shell. It executes commands with escalated privileges. On the other hand, you *can* start sudo with sudo -i which, at least according to the manpage, would start a login shell and set all the env variables. What I am not sure is whether sudo -i asks you for the root password or the sudo password.... W -- Tried to play my shoehorn... all I got was footnotes! Sortir en Pantoufles: up 33 days, 19:10 -- [email protected] mailing list
