pcp
[Top] [All Lists]

Re: Daemons not started from rpm postop

To: pcp@xxxxxxxxxxx
Subject: Re: Daemons not started from rpm postop
From: Nathan Scott <nscott@xxxxxxxxxx>
Date: Thu, 18 Sep 2008 11:41:18 +1000
In-reply-to: <1221701500.4827.18.camel@xxxxxxxxxxxxxxxxxx>
References: <1221701500.4827.18.camel@xxxxxxxxxxxxxxxxxx>
Sender: pcp-bounce@xxxxxxxxxxx
On Thu, 2008-09-18 at 11:31 +1000, Nathan Scott wrote:
> Hi all,
> 
> Does anyone know the reason for not starting pmcd after an rpm
> install?  I've had a request for that, to reduce steps required
> to do a pcp install/upgrade on large numbers of machines ... is
> there any good reason not to do this?
> 
> Only reason I can think of is that if pcp is being installed as
> part of a larger set of rpms, on a fresh install, the prereqs
> might not be there yet?  Or networking not started, etc... but
> it should be harmless to try to (re)start pcp, shouldn't it?

Also, I just noticed a long-time PITA I've had, but never got
round to looking into - the rpm postop explicitly chkconfig's
pmie and pmproxy off.  This means on an upgrade, previously
enabled pmie and pmproxy state is blown away.

Thats clearly a bug - I'll remove those two lines shortly in
my branch.

cheers.

--
Nathan


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