Don't know if this is a bug, but locate acts strange now and
I notice that updatedb keeps on running (forever?)
"ps aux" shows:
Should there be something excluded in slocate? Or is this
that's update (bdflush), which is the kernel's cache
flushing-daemon. It doesn't have anything to do with
OOPS!! Very sorry!
But the reason I got confused was: running "updatedb" (and not
slocate, sorry) hangs. (and I thought it was launched at startup, and
confused it with update)
Should I exclude something from updatedb?
If you do 'strace -o output updatedb', and then look at
the output file when it hangs, where is it hanging?
*** This bug has been marked as a duplicate of 2682 ***
Well, it seems to hang when doing "chdir(".automount")". Do you want
me to give you the details given by strace?
I've replace updatedb in slocate-1.6-1 to more perfectly imitate
the behavior of the findutils updatedb. This means that certain
directories and NFS or smb mount points will not be searched while
building the slocate database.