Your message dated Sun, 30 Mar 2008 17:21:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 1.2.5+
has caused the Debian Bug report #416156,
regarding PID handling in init.d is fragile
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
416156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416156
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Package: up-imapproxy
Version: 1.2.6-1
found #416156 1.2.4-10
thanks
This bug was fixed as of 1.2.5-1 (never uploaded to Debian).
My patch adding this functionality was
--- End Message ---
