pcp
[Top] [All Lists]

Re: Review: PCP & pmlogger take too long to start

To: Nathan Scott <nscott@xxxxxxxxxx>
Subject: Re: Review: PCP & pmlogger take too long to start
From: Michael Newton <kimbrr@xxxxxxx>
Date: Tue, 3 Jul 2007 10:41:45 +1000
Cc: pcp@xxxxxxxxxxx
In-reply-to: <1183417678.15488.257.camel@xxxxxxxxxxxxxx>
References: <Pine.SGI.4.58.0706271012280.2186626@xxxxxxxxxxxxxxxxxxxxxxx> <Pine.SGI.4.58.0706271124250.2186626@xxxxxxxxxxxxxxxxxxxxxxx> <Pine.SGI.4.58.0706271715321.2351218@xxxxxxxxxxxxxxxxxxxxxxx> <1182996127.15488.102.camel@xxxxxxxxxxxxxx> <Pine.SGI.4.58.0706291810180.4792701@xxxxxxxxxxxxxxxxxxxxxxx> <1183355238.15488.217.camel@xxxxxxxxxxxxxx> <1183356141.15488.223.camel@xxxxxxxxxxxxxx> <Pine.SGI.4.58.0707021658520.7708406@xxxxxxxxxxxxxxxxxxxxxxx> <1183417678.15488.257.camel@xxxxxxxxxxxxxx>
Sender: pcp-bounce@xxxxxxxxxxx
On Tue, 3 Jul 2007, Nathan Scott wrote:
> On Mon, 2007-07-02 at 17:02 +1000, Michael Newton wrote:
> > you know pmlogger is through its initialisation, but now
> > you need to give it a little time to finish cleaning up the
> > connection you have just relinquished, so as to be ready to
> > talk to a real client.
>
> That bit I don't buy - the startup script uses pmlc to connect
> as this guarantees that pmlogger is started up and ready - there
> isn't any "little time" after a pmlc connection where pmlogger is
> not available for another connection.  It seems that additional
> sleep there is redundant - I'll ask Ken though when he's back if
> he can remember why it was added (any chance you can do some rlog
> sleuthing, see if it was added in response to a bug?).

p_rlog only shows me back to 1.22, which still has the pre-exit sleep

> Really odd that it was a full three second sleep too.

5, i believe

i'll make the agreed changes and retest. Unless something else happens in
the meantime, i'll commit it.. this is taking too log.. minor fix-ups can
be done later

Dr.Michael("Kimba")Newton  kimbrr@xxxxxxx

<Prev in Thread] Current Thread [Next in Thread>