[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #15384] find misbehaves when parent directory is not readable

From: Eric Blake
Subject: [bug #15384] find misbehaves when parent directory is not readable
Date: Wed, 22 Aug 2007 18:16:19 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20070725 Firefox/ Mnenhy/

Update of bug #15384 (project findutils):

                  Status:                    None => Fixed                  
           Fixed Release:                    None => 4.3.2                  


Follow-up Comment #3:

Actually, the failure when '.' can't be found (for example, because a parent
is unsearchable) was introduced in 4.3.3; I'll open a separate report for

This report deals with unreadable, but searchable parents.  Indeed, fts makes
a difference:

$ mkdir -p private/d
$ touch private/d/a
$ ~/findutils-4.3.8/find/find /tmp/private/d
$ chmod a-rw /tmp/private
$ ~/findutils-4.3.8/find/find /tmp/private/d
$ ~/findutils-4.3.8/find/oldfind /tmp/private/d
/home/ericb/findutils-4.3.8/find/oldfind: `/tmp/private': Permission denied

At this point, since we are about to create a stable 4.4 branch where the
fts()-based find works, do we still need to worry about the home-grown
oldfind, which still has the bug?

And do we go ahead and add the patch attached to this bug to the 4.3.x
testsuite, when it will only pass on one of the two implementations?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]