On Tue, October 9, 2012 5:03 pm, Nicolas Richard wrote: >>>>>> "Joost" == J Roeleveld <jo...@antarean.org> writes: > > Joost> Nicolas Richard <theonewiththeevill...@yahoo.fr> wrote: > >> Here is the output of the relevant (at least I thought they were) > >> commands. Can somebody explain to me why I still have > >> /usr/local/texlive/*2011*/bin/i386-linux in the first sudo output > > >> youngfrog@geodiff-mac3 ~ $ sudo bash -c 'echo $PATH' > >> > /bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/local/texlive/2011/bin/i386-linux > > >> youngfrog@geodiff-mac3 ~ $ grep -v '^#\|^$' /etc/environment > >> > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.5.3:/usr/local/texlive/2012/bin/i386-linux:/root/bin > > Joost> I can see several /usr/local/... paths in your > Joost> /etc/environment. > > > Hello Joost, > > Yes, I see them too, but they are pointing to the more recent 2012 > release of texlive, not the older 2011 one. What I don't understand is > where /sudo/ finds the environment when called without the "-i" option > (and in particular, that entry for texlive 2011). The manpage seems to > say that it simply uses the current environment (quoting the manpage : > "Note, however, that the actual PATH environment variable is not > modified and is passed unchanged to the program that sudo executes.") > but that does not seem right. > > -- > N.
What do you get with "echo $PATH" when not using sudo? -- Joost
