pcp
[Top] [All Lists]

Re: [pcp] pmcd gives up on slow starting Perl PMDA

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pmcd gives up on slow starting Perl PMDA
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 25 Mar 2014 18:45:36 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <533204C5.10104@xxxxxxxxxxxxxxxx>
References: <532C975F.4020808@xxxxxxxxxxx> <532F56BC.9040500@xxxxxxxxxxxxxxxx> <146115274.4201680.1395623527453.JavaMail.zimbra@xxxxxxxxxx> <53300840.1070009@xxxxxxxxxxxxxxxx> <1918399066.396500.1395783563283.JavaMail.zimbra@xxxxxxxxxx> <533204C5.10104@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: eph60lJBR292QBhhSjoNNyj3Kk+Dvg==
Thread-topic: pmcd gives up on slow starting Perl PMDA

----- Original Message -----
> > ...
> As I think I said in an earlier mail (a couple of days ago), this will
> require a new method for Perl (and Python I suspect if that wrapper
> follows the Perl model) to force the connect earlier than the run()
> method, I suggested connect().

Sorry about my reply tardiness (you didn't get the NOTREADY PDU I sent?)
I've been attempting to keep my head down, coding.  :)  Yes, both of the
languages wrappers will need to be tweaked as you say; python is wrapped
slightly differently but mainly in its object-oriented-ness:

> The example above needs to be tested to ensure that the add_metric() and
> add_indom() logic works after the connect() ... if this is OK, then we

That will work just fine I expect.  Those add* calls update in-memory
data structures - the gears only engage when run() is called.

cheers.

--
Nathan

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