find giving bad status?

[Geoff Coleman]

In article <16507 at smoke.brl.mil> gwyn at smoke.brl.mil (Doug Gwyn) writes:
>
>"find: bad status" messages simply mean that a stat() of the file failed.
>The usual cause of this is a symbolic link whose target does not exist.


	Ther is also a bug or feature in find that causes

find . -depth -print 

To give bad status messages. We pulled apart the source one day
and found that find was walking the  directory tree and stating 
against ./<directory . It's been a couple of years now so I forget
the exact fix in the code.

NOTE: This was on a 3B21000-70 running System V 3.2


Geoff Coleman