Package: imapproxy Version: 1.2.4-10 Severity: important The pid-handling of imapproxy is pretty fragile, as documented in #369020 amongst others. The current workaround of writing a new pidfile after start based on 'ps ax' output is, eh, fragile at best, and actually pretty bad.
The proper solution would be to patch imapproxy so that it writes out a pidfile itself, like proper daemons should. This way, you can forget about start-stop-daemon's --make-pidfile, which breaks when the admin sets foreground-mode to off. --Jeroen -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-xen-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
