Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!elroy.jpl.nasa.gov!ames!dftsrv!jagmac2.gsfc.nasa.gov!jim From: jim@jagmac2.gsfc.nasa.gov (Jim Jagielski) Newsgroups: comp.unix.aux Subject: find and root directories Message-ID: <3163@dftsrv.gsfc.nasa.gov> Date: 20 Aug 90 15:32:45 GMT Sender: news@dftsrv.gsfc.nasa.gov Reply-To: jim@jagmac2.gsfc.nasa.gov (Jim Jagielski) Distribution: na Organization: NASA Goddard Space Flight Center Lines: 34 Under 2.0, find dies a horrible death if one of the directories attached at / is not readable and "executable" by the user invoking find. This only happens if / is given as the pathname to find... For example: ----------------------------- Assume /nolook is mode 700 find / -print find: cannot chdir to /nolook /* This no works */ find: bad directory tree cd / find . -print /* This works just dandy */ cd ~ find /. -print /* natch this too... */ ----------------------------- For some reason, using absolute pathnames confuses find when looking around /. If "protected" directories are other places (such as /usr/spool/cron) then find works fine; it tells you it can't chdir there and goes on. If it's in /, then all bets are off. However, if you use a relative pathname, then find works just dandy.... Anybody at Apple know why? And will there be a fix? -- ======================================================================= #include =:^) Jim Jagielski NASA/GSFC, Code 711.1 jim@jagmac2.gsfc.nasa.gov Greenbelt, MD 20771 "Kilimanjaro is a pretty tricky climb. Most of it's up, until you reach the very, very top, and then it tends to slope away rather sharply."