--with-secure-path=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/kde/3.5/sbin:/usr/kde/3.5/bin:/usr/qt/3/bin As per my understanding, this is only going to make problems, if user doesn't understand what is he doing, what better is that going to be? At least, there should be an useflag not to enable it! Reproducible: Always Actual Results: I can't load any other PATH residing programs without full path to them after sudo! Nightmare.
if you spend a little time googling, you'll see this is how sudo has always worked for everyone considering $PATH changes a lot, adding a USE flag to set secure-path wont work just do what everyone else does: sudo env PATH="$PATH" ........
Please explain more... What is the reason behind this?
>considering $PATH changes a lot, adding a USE flag to set secure-path wont work Misunderstood: a useflag not to use it!
read the sudo documentation
