Jim Meyering wrote:
> You can probably find out by rerunning that test with e.g.,
>
> SHELL=bash make check -C tests TESTS=cp/fail-perm VERBOSE=yes
Find attached the test-suite.log that this produced.
Here's what's going on:
$ ls -ld DD
drwx------+ 3 haible haible 3 Sep 2 17:23 DD
$ ls -ld DD/D
drwxrwxr-x+ 2 haible haible 2 Sep 2 17:23 DD/D
$ ls -l DD/D
total 0
$ ls -la DD/D
total 10
drwxrwxr-x+ 2 haible haible 2 Sep 2 17:23 .
drwx------+ 3 haible haible 3 Sep 2 17:23 ..
$ /bin/rmdir DD/D
rmdir: directory "DD/D": Search or write permission needed
$ truss /bin/rmdir DD/D
...
rmdir("DD/D") Err#13 EACCES
...
This is on an NFS volume.
> A blind patch (without understanding, always risky),
> this might solve the problem:
>
> diff --git a/tests/cp/fail-perm b/tests/cp/fail-perm
> index 404c83e..4009c00 100755
> --- a/tests/cp/fail-perm
> +++ b/tests/cp/fail-perm
> @@ -53,6 +53,6 @@ cp --target-directory=symlink F 2> out && fail=1
> sed 's/: The file access permissions.*/: Permission denied/'<out>o1;mv o1 out
> compare out exp || fail=1
>
> -chmod 700 D
> +chmod 700 D DD
>
> Exit $fail
No, it doesn't help.
Bruno
--
In memoriam Robert Mensah <http://en.wikipedia.org/wiki/Robert_Mensah>