find: bug or feature?

[J. Milgram]

Hi,

am getting unexpected results from find. Can't figure out if it's me
(often the case, with find) or a bug. Can you help?

This pretty much says it all:

%:/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? Obviously has something to do
with depth option.

thanks,

Judah


----
Judah Milgram                            (301) 227-1536 (voice)
Sea-Based Aviation, Code 5301            (301) 227-2584 (fax)
Carderock Division, NSWC                 DSN 287-1536
9500 MacArthur Blvd.                     address@hidden
West Bethesda, MD  20817-5700