Fixed in Lucid.
mlocate (0.21.1-3) unstable; urgency=low
[ Adeodato Simó ]
* Remove the "mlocate" group on purge. No other files than the mlocate.db
database should belong to said group, and since it also gets removed on
purge, it should be safe to remove the group as well. (Closes: #
Similar to #431925 which requests similar things for glusterfs and /net. Low
hanging fruit, big gain.
See list of notified people. Thanks.
--
updatedb should exclude sshfs by default
https://bugs.launchpad.net/bugs/371749
You received this bug notification because you are a member of Ubuntu
Bugs
Wow, still not fixed? This is an easy fix guys. Just add fuse.sshfs to
PRUNEFS in /etc/updatedb.conf ...
--
updatedb should exclude sshfs by default
https://bugs.launchpad.net/bugs/371749
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
This needs to be fixed. I recently changed my sshfs mountpoint from
under /media to my home directory, and that resulted in my nightly
mlocate scripts filling my disk. What makes this worse is when you are
using the -o follow_symlinks option, which can result (in my case) in
infinitely large paths,
** Changed in: mlocate (Ubuntu)
Importance: Undecided => Medium
** Changed in: mlocate (Ubuntu)
Status: New => Triaged
--
updatedb should exclude sshfs by default
https://bugs.launchpad.net/bugs/371749
You received this bug notification because you are a member of Ubuntu
Bugs, which is
