Jeroen van Wolffelaar wrote:
> [snip]
>>> Fine. I did put the function back where it was though, instead of moving
>>> it way below, because the stuff in between can hang (for example, when
>>> failing to connect, it'll indefinitely retry every 15 seconds, causing
>>> 'start' to hang).
>>>
>>>
On Wed, Mar 28, 2007 at 05:01:09PM +0200, José Luis Tallón wrote:
> Jeroen van Wolffelaar wrote:
> > It's a misconfiguration, sure, but one that happens on default install
> > (out of the box imapproxy is misconfigured? Well, it was in my case, but
> > probably related to the fact that I don't actu
On Wed, Mar 28, 2007 at 08:26:27AM +0200, José Luis Tallón wrote:
> Jeroen van Wolffelaar wrote:
> > Uploaded as NMU, because I actually made some changes.
> >
> Reviewed them. Gotta ACK, anyway.
> (You are right in the changes you made, I would have done it differently)
That's of course fine,
Jeroen van Wolffelaar wrote:
> Can you please bounce this mail to the bug log? I didn't want to do so
> because this is private mail, but this really really should be part of
> the bug log.
>
> On Wed, Mar 28, 2007 at 12:13:39AM +0200, José Luis Tallón wrote:
>
>> Jeroen van Wolffelaar wrote:
>>
Original Message
Subject:Re: Bug#416156: PID handling in init.d is fragile
Date: Wed, 28 Mar 2007 04:27:06 +0200
From: Jeroen van Wolffelaar <[EMAIL PROTECTED]>
To: José Luis Tallón <[EMAIL PROTECTED]>
CC: Jeroen van Wolffelaar <[EMAIL PRO
Oops, I actually NMU'd for this bug (#415954), not for #416156.
--Jeroen
--
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
--- Begin Message ---
On Tue, Mar 27, 2007 at 11:53:42PM +0200, Jeroen van Wolffelaar wrote:
> On Tue, Mar 27,
On Tue, Mar 27, 2007 at 11:53:42PM +0200, Jeroen van Wolffelaar wrote:
> 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
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 writi
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,
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 solut
10 matches
Mail list logo
