Re: find: bug or feature?

[Stepan Kasal]

Hello,

On Mon, Dec 30, 2002 at 08:51:17AM -0500, J. Milgram wrote:
> %:/tmp/demo: find --version
> GNU find version 4.1
> %:/tmp/demo: find . -ls
> 919891    4 drwxr-xr-x   3 milgram  root         4096 Dec 30 08:42 .
> 2541885    4 drwxr-xr-x   3 milgram  root         4096 Dec 30 08:42 ./foo
> 2541890    4 drwxr-xr-x   3 milgram  root         4096 Dec 30 08:42 ./foo/bar
> 2541891    4 drwxr-xr-x   3 milgram  root         4096 Dec 30 08:42 
> ./foo/bar/tmp
> 2541892    4 drwxr-xr-x   2 milgram  root         4096 Dec 30 08:47 
> ./foo/bar/tmp/cache
> %:/tmp/demo: find . -depth \( -type f -o -type l -o -type d -empty \)
> ./foo/bar/tmp/cache
> find: ./foo/bar/tmp: No such file or directory
> find: ./foo/bar: No such file or directory
> find: ./foo: No such file or directory
> find: .: No such file or directory
> 
> It properly reported ./foo/bar/tmp/cache as an empty directory, but why
> the warnings for the parent directories? [...]

the latest development version, 4.1.7, seems to have this fixed.

You can get it from the CVS this way:
cvs -z3 -d:pserver:address@hidden:/cvsroot/findutils login
[hit enter]
cvs -z3 -d:pserver:address@hidden:/cvsroot/findutils co findutils

(It's not available on alpha.gnu.org, sorry.)

HTH,
        Stepan Kasal