Mike Frysinger wrote:
> running as root i see these test failures:
Thanks for doing this testing.
[...trimmed log...]
> 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?
> + case $rm_version in
> + echo './../../../tests/rm/fail-2eperm: cannot access just-built rm as user
> nobody'
> ./../../../tests/rm/fail-2eperm: cannot access just-built rm as user nobody
> + fail=1
It has failed before it really got started with the test. It is still
trying to set things up. The code is:
# Try to ensure that $NON_ROOT_USERNAME can access
# the required version of rm.
rm_version=`setuidgid $NON_ROOT_USERNAME env PATH="$PATH" rm --version|sed -n
'1s/.* //p'`
case $rm_version in
$PACKAGE_VERSION) ;;
*) echo "$0: cannot access just-built rm as user $NON_ROOT_USERNAME" 1>&2
fail=1 ;;
esac
Perhaps this is a red herring but I am wondering how 'nobody' is set
up on your system. I have:
id nobody
uid=65534(nobody) gid=65534(nogroup) groups=65534(nogroup)
Does this work for you?
./src/setuidgid nobody env PATH=$PWD/src:$PATH rm --version
How about this?
./src/setuidgid nobody id
Thanks again for doing this testing.
Bob
_______________________________________________
Bug-coreutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-coreutils
