On Tue, Mar 27, 2007 at 10:54:58PM +0200, José Luis Tallón wrote: > Jeroen van Wolffelaar wrote: > > 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. > Fixed. Will submit the patch ASAP
Why didn't you attach it? I'm pretty busy tomorrow, and want to get this fixed ASAP. I mean, the plan is to release this weekend... --Jeroen -- 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]
