Follow-up Comment #5, bug #47261 (project findutils):
Could it be a case of automounting kicking in? If your file is hidden behind a
mount point, maybe the first run triggers the mount to automount but doesn't
descend, and the second one is able to descend into the (now-mounted)
location?
__
Follow-up Comment #4, bug #47261 (project findutils):
I wonder if something is special about /sys. What happens if you invoke find
like this:
sudo find / \( -path /sys -prune \) , -iname 'firefox_binary.py'
Also do you definitely need to run "find" the first time to see the difference
in beh
Follow-up Comment #3, bug #47261 (project findutils):
It's also interesting to see the contents of the struct stat instances we get
for the stat calls. Could you use "strace -v" rather than plan strace
please?
___
Reply to this item at:
Follow-up Comment #2, bug #47261 (project findutils):
Some other things:
1. what file systems types are being used for the affected machine?
2. I assume that the same problem exists with -name as with -iname, but could
you check? What about -regex?
3. You say the problem happens "the first ti
Update of bug #47261 (project findutils):
Severity: 3 - Normal => 4 - Important
Status:None => Need Info
Assigned to:None => jay
