On 4/29/11 12:25 PM, Johan Hattne wrote: > Bash Version: 4.2 > Patch Level: 8 > Release Status: release > > Description: > Following a report about a year ago, the determination of the > executable status used by bash's built-in test command was changed. > The original issue was that the access(2) family of functions may > indicate success for X_OK, even if the file does not actually have > any execute permission bits set. This is allowed by the > specification for historical reasons, even though discouraged for new > implementations > > (http://pubs.opengroup.org/onlinepubs/9699919799/functions/faccessat.html). > On FreeBSD which provides faccessat(2) as well as eaccass(2), this > causes test -x to report false positives.
Thanks for the update. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/