Adam Conrad <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 15, 2008 at 07:16:12PM -0500, Michael Stone wrote:
>> Could you send an strace from one of the non-working systems? That might
>> be enough to figure out what's going wrong and whether it can be worked
>> around.
>
> Attached.
Thanks.
Please double-check the version of the rm binary you
used to create that strace output.
When I try to reproduce the situation (no openat support
and no /proc), the fchdir-based openat emulation works
just fine. But I'm merely simulating the situation,
and am actually running tests on a system with a recent
kernel, so there may be other factors.
That said, ...
I used a version of rm from the trunk (i.e., post-coreutils-6.10)
and comparing an strace of my working rm -r dir/ command to yours
shows fundamental differences that make me think your version of
rm is out of date. Maybe even from coreutils-5.9x.
If you can confirm you're using something based on 6.10, please
also attach config.status and lib/config.h.
-----------------------
For the record, here's what I did:
Simulate the lack of openat functions:
ac_cv_func_openat=no ./configure && make && make check
All tests passed.
Next, pretend we don't have /proc/self/fd support either, by changing
the openat-emulation code to use nonexistent /proc/self/FD:
perl -pi -e 's,/proc/self/fd,/proc/self/FD,' lib/openat-proc.c \
tests/du/long-from-unreadable tests/rm/inaccessible
That passed all tests, too, and gave the strace results that looked
so different from yours.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
