Follow-up Comment #1, bug #33207 (project findutils):
I think it's unlikely that this problem is NFS-specific.
Are you sure it is find which is consuming all the memory? Not sort? How
many files, in total, are involved? (you can figure this out by running
locate -S on a correct database)
What is the command line of the find process which is using up all the
system's memory? Do you get the same effect if you run the same find command
on the NFS server directly, with the local filesystem paths (I suppose you
will need to adjust the directory names)?
What is the newest findutils 4.4.x release which is not affected by this
problem?
Does a system call trace (with e.g. strace on Linux or its equivalent on the
NFS server) reveal any difference between the affected and unaffected
releases, or any otherwise interesting behaviour?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?33207>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
