Re: [PATCH] tests: adjust PATH to include /usr/sbin for filefrag-using tests

[Bernhard Voelker]

On 11/23/2011 10:31 PM, Bob Proulx wrote:
> Jim Meyering wrote:
>> The point is that the separation is not clear.
>> Even /sbin programs like mkfs.* can be useful to non-root users.
>> I use a few of those in parted tests.
>> Also, ifconfig is useful to non-root users, yet resides in /sbin.
> 
> I am sure that you like me always add /usr/local/sbin:/usr/sbin:/sbin
> to your PATH as a normal non-root user.  This shields us from most of
> those problems.  And sometimes hides the problem.
> 
>> Thus, by omitting /sbin and /usr/sbin, that version of sudo is
>> causing trouble.  Fedora made the same change to sudo, but ended
>> up reverting it due to all of the trouble it caused.
> 
> The upstream sudo has been making some incompatible changes with
> regards to PATH specifically around secure_path (and running configure
> with --with-secure-path).  This has slowly been rippling down.  I
> apologize in advance but this is going to be a Debian centered view.
> But as they say, write what you know.

Again, I don't think it is related to sudo. It is /bin/login.

I even changed to runlevel 3, renamed sudo, did the login on tty2, and
then "make check TESTS=cp/fiemap-perf" was skipped in the same way.
Sudo is not used here. And such sbin paths have never been included
for non-root users on SuSE and AFAIK on Solaris.

According to my /etc/profile, such admin paths are only added for root:

    if test "$UID" = 0 ; then
        test -d /opt/kde3/sbin  && PATH=/opt/kde3/sbin:$PATH
        PATH=/sbin:/usr/sbin:/usr/local/sbin:$PATH
    fi

Am I missing something? What's the connection to sudo here?

Have a nice day,
Berny