[bugs #11175] find does unwanted permission check on pruned directory

[James Youngman]

This mail is an automated notification from the bugs tracker
 of the project: findutils.

/**************************************************************************/
[bugs #11175] Latest Modifications:

Changes by: 
                James Youngman <address@hidden>
'Date: 
                Sat 12/04/04 at 13:19 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
         Assigned to | None                      | jay


------------------ Additional Follow-up Comments ----------------------------
I have now fixed this in CVS.   The code change is small but has a profound 
effect on the treatment of the files specified on the find command line (they 
are now treated exactly like any other directory we discover during a search, 
except for what we do when we leave a subdirectory immediately below them).   
Would you be in a position to exercise the CVS version of find a bit before I 
make a proper release with this bugfix in it?






/**************************************************************************/
[bugs #11175] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=11175>
Project: findutils
Submitted by: Geoff Clare
On: Tue 11/30/04 at 11:56

Category:  find
Severity:  5 - Average
Item Group:  None
Resolution:  Fixed
Privacy:  Public
Assigned to:  jay
Originator Name:  
Originator Email:  
Status:  Open
Release:  4.2.8
Fixed Release:  None


Summary:  find does unwanted permission check on pruned directory

Original Submission:  Find reports an error in the following situation:

$ mkdir noxdir
$ chmod a-x noxdir
$ find * -prune -type d -print
find: noxdir: Permission denied
$ echo $?
1

Since the directory will be pruned, find should not be checking its 
permissions.  It should write "noxdir" to stdout (and its exit status should be 
0).

Follow-up Comments
------------------


-------------------------------------------------------
Date: Sat 12/04/04 at 13:19         By: James Youngman <jay>
I have now fixed this in CVS.   The code change is small but has a profound 
effect on the treatment of the files specified on the find command line (they 
are now treated exactly like any other directory we discover during a search, 
except for what we do when we leave a subdirectory immediately below them).   
Would you be in a position to exercise the CVS version of find a bit before I 
make a proper release with this bugfix in it?












For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=11175>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/