[bug #19605] find does not report symlink loop when trying to follow symlinks

[Geoff Clare]

Follow-up Comment #5, bug #19605 (project findutils):

I take your point about d_type (the system I tried it on does have d_type). 
I still think that find should report this error.  With the -L option find
follows symlinks, so all the pathnames it writes to stdout should be files
that exist when symlinks are followed.  If "a" is a symlink loop it
effectively does not exist when symlinks are followed, because the pathname
does not resolve successfully.

Here is a slightly different case that may be more convincing:

$ ln -s a b
$ ln -s b a
$ find -L a/foo
a/foo

Here find is reporting that a file called a/foo exists, which is obviously
not the case.

P.S. I have tried the patch, and I can confirm that it fixes the problem.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?19605>

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