Speaking of ls(1)...
$ mkdir Arghh
$ touch Arghh/{one,two,three}
$ ls Arghh
one three two
$ chmod a-x Arghh
$ ls Arghh && echo SUCCESS
SUCCESS
$ ls -l Arghh && echo SUCCESS
SUCCESS
ARGGGGHHHHH!!!! :-)
This is not the expected behavior. If a directory does not have
search permission, but it has read permission, a plain "ls" (or "ls -i")
should list its contents, while "ls -l" should fail. And still worse,
when ls fails to list the non-searchable directory contents, it
does _not_ return an error code.
I tried to find the cause of this behavior in the ls source code,
but it uses the fts(3) functions, which I am not used to.
Cheers,
-- JMA
****** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ******
** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein **
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
