This bug was fixed in the package mlocate - 0.26-1ubuntu1

---------------
mlocate (0.26-1ubuntu1) saucy; urgency=low

  * Resynchronise with Debian (locking fix closes LP: #731632).  Remaining
    changes:
    - Add ecryptfs, fusesmb, and devtmpfs to PRUNEFS.
    - Add /home/.ecryptfs to PRUNEPATHS.

mlocate (0.26-1) unstable; urgency=low

  * New upstream release.  Closes: #669368
    - Stops using PATH_MAX.  Closes: #610209
  * The filesystem type for Lustre is lustre, not lustre_lite.  Update
    updatedb.conf accordingly.  Closes: #660781
  * Fix up locking in cron.daily.  Closes: #611096
  * rm -rf /var/lib/mlocate on purge, don't just take out single files.
    Closes: #542616
 -- Colin Watson <[email protected]>   Thu, 20 Jun 2013 15:03:51 +0100

** Changed in: mlocate (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/731632

Title:
  mlocate cron job doesn't respect its lockfile

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/731632/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to