Follow-up Comment #3, bug #51345 (project findutils):
Okay, so this happens after a fresh reboot.
Thanks for the strace logs; but please compress them the next time because it
was 12M+37M to download.
If I got it right, then the last directory processed in the 1st run was
/proc/sys/kernel/debug/tracing/events/raw_syscalls/sys_exit
and then ended normally while the second run continued with
/proc/sys/kernel/debug/tracing/instances
Interestingly, the 1st run didn't find any match:
there was no write() system call at all. Really strange.
Back to my other question: did you try with a newer version of find,
either the latest release 4.6 or even a version built from the Git
repository?
I mean, 4.4.2 is about eight years old, and a lot has changed since then.
I didn't find an obvious bug fix for this in the NEWS by a very brief look,
but I don't want to spend much time riding a dead horse.
Thanks & have a nice day,
Berny
P.S. It is probably a good idea to skip file system types like /proc and
/sys,
because they may contain loops and usually don't contain the information one
is searching for, so I usually use the -xdev option when searching from the
root directory '/'.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51345>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
