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
> This way, you can forget
> about start-stop-daemon's --make-pidfile, which breaks when the admin
> sets foreground-mode to off.
>
Thanks, Jeroen
J.L.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
