[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fail-2eperm (was: coreutils-6.9.90 test results for x86_64-linux-gnu
From: |
Mike Frysinger |
Subject: |
Re: fail-2eperm (was: coreutils-6.9.90 test results for x86_64-linux-gnu) |
Date: |
Tue, 4 Dec 2007 00:01:39 -0500 |
User-agent: |
KMail/1.9.7 |
On Monday 03 December 2007, Bob Proulx wrote:
> Mike Frysinger wrote:
> > running as root i see these test failures:
> > pretty sure the first one is known
> > FAIL: fail-2eperm.log (exit: 1)
>
> + rm --version
> rm (GNU coreutils) 6.9.90
> +++ id -u nobody
> ++ coreutils_non_root_uid=65534
>
> Looks like your nobody user is 65534 which is typical.
>
> > + rm_version=6.9
>
> Shouldn't that say 6.9.90? I get 6.9.90. The log showed 6.9.90
> earlier.
>
> The code is:
>
> rm_version=`setuidgid $NON_ROOT_USERNAME env PATH="$PATH" rm
> --version|sed -n '1s/.* //p'`
>
> Try this:
>
> ./src/rm --version | sed 1q
> rm (GNU coreutils) 6.9.90
>
> ./src/setuidgid nobody env PATH=$PWD/src:$PATH rm --version | sed -n
> '1s/.* //p' 6.9.90
>
> Can you look at that more closely and figure out why the output is
> inconsistent?
because the nobody user does not have access to
the /full/path/to/the/directory which the new `rm` resides
one of the directories in the absolute tree is actually go-rwx, so i guess the
failure cascades from there
-mike
signature.asc
Description: This is a digitally signed message part.