Re: ls when acl() is busy [was: ls slow on top-level directory]

2005-06-28 Thread Corinna Vinschen
On Jun 28 03:24, Eric Blake wrote: [bug-coreutils: posting this cygwin question upstream] Corinna Vinschen wrote: Along these lines, we had a short discussion on the developers list and we're wondering if it's necessary that ls prints this error message at all. The message is generated

Re: ls when acl() is busy [was: ls slow on top-level directory]

2005-06-28 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Corinna Vinschen on 6/28/2005 2:34 AM: Hmm - murky waters here. It would be a simple one-line fix to coreutils/lib/acl.c to ignore EBUSY as a non-error, and POSIX has no requirements per se that a failure of acl() should imply a failure

Re: ls when acl() is busy [was: ls slow on top-level directory]

2005-06-28 Thread Lasse
Eric Blake wrote: According to Corinna Vinschen on 6/28/2005 2:34 AM: However, IMHO, ls should be changed to just print no error message, if file_has_acl() returns -1 and errno is set to EBUSY, and the file should simply be treated as a file with no ACL. That's the least intrusive way, IMHO.

ls when acl() is busy [was: ls slow on top-level directory]

2005-06-27 Thread Eric Blake
[bug-coreutils: posting this cygwin question upstream] On Jun 27 14:50, Will Parsons wrote: I notice that ls reports: /bin/ls: hiberfil.sys: No such file or directory /bin/ls: pagefile.sys: No such file or directory ls hitab completes to ls hiberfil.sys, and shows the same