Package: mlocate Version: 0.22.2-1 Severity: normal Hi,
The rudimentary locking implemented in /etc/cron.daily/mlocate suffers from several problems. 1. It's racy: two cron jobs can start together (both -e test can fail, then both touch commands can succeed. I agree it's mostly theoretic. 2. It unconditionally removes the lock file on exit, so only refuses to run on the first try if another instance is already running. I suggest to depend on lockfile-progs and use those tools for reliable locking. /etc/cron.daily/standard provides a rather elaborate example. Thanks, Feri. -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.37-trunk-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mlocate depends on: ii adduser 3.112+nmu2 add and remove users and groups ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib mlocate recommends no packages. mlocate suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
