Package: mlocate Version: 0.18-2 Severity: normal Hello.
I currently have two instances of updatedb.mlocate running, both started by cron.daily on two subsequent days. The first one apparently took more than one day to complete... so in such case there's no need to start another one. Some locking mechanism would be much welcome IMHO. Hope this helps, Best regards, -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mlocate depends on: ii adduser 3.106 add and remove users and groups ii libc6 2.7-6 GNU C Library: Shared libraries mlocate recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
