[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #56410] find -L doesn't follow symlinks outside the specified searc
From: |
Bernhard Voelker |
Subject: |
[bug #56410] find -L doesn't follow symlinks outside the specified search scope |
Date: |
Wed, 5 Jun 2019 02:22:18 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0 |
Follow-up Comment #14, bug #56410 (project findutils):
We're always interested in improving things, so thanks again for reporting
an issue like this.
The implementation of -L is correct - or at least we don't have a proven
example where it wouldn't be -; (only) the search, i.e., the tests, are based
on the file referenced by the file a symbolic link points to.
Or in the words of POSIX:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/find.html
Cause the file information and file type evaluated for each symbolic link
encountered
as a path operand on the command line or encountered during the traversal of a
file
hierarchy to be those of the file referenced by the link, and not the link
itself.
I'm trying to find the documentation which would make you as a our user
think that -L would let -print or "-exec ... {}' +" use the resolved path
name.
Would you point us to such unclear passage, or even better provide a clearer
phrasing as a matter for discussion?
Thanks & have a nice day,
Berny
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56410>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/