Re: [trinity-users] the state of sudo

Le 26/11/2011 20:38, Timothy Pearson a écrit : For the moment, with Trinity's sudo, sudo `which ...` works with executables in $HOME/bin that aren't in the secure path of sudo (AFAIK 'which' is called before 'sudo'). I just replaced /usr/bin/sudo, and /usr/lib/sudo/sudo_noexec.so by debian versions (and added /usr/lib/sudo/sudoers.so) and everything works. $ sudo `which kwrite` Error: "/var/tmp/kdecache-eldi" is owned by uid 1000 instead of uid 0. $ sudo `which konqueror` Error: "/var/tmp/kdecache-eldi" is owned by uid 1000 instead of uid 0. Error: "/tmp/kde-eldi" is owned by uid 1000 instead of uid 0. Error: "/tmp/ksocket-eldi" is owned by uid 1000 instead of uid 0. Error: "/var/tmp/kdecache-eldi" is owned by uid 1000 instead of uid 0. Error: "/var/tmp/kdecache-eldi" is owned by uid 1000 instead of uid 0. Error: "/var/tmp/kdecache-eldi" is owned by uid 1000 instead of uid 0. Error: "/var/tmp/kdecache-eldi" is owned by uid 1000 instead of uid 0.