pcp
[Top] [All Lists]

Re: PCP start/stop script regression

To: Michael Newton <kimbrr@xxxxxxx>
Subject: Re: PCP start/stop script regression
From: Nathan Scott <nscott@xxxxxxxxxx>
Date: Wed, 11 Jul 2007 11:04:09 +1000
Cc: Mark Goodwin <markgw@xxxxxxx>, pcp@xxxxxxxxxxx
In-reply-to: <Pine.SGI.4.58.0707041636040.10924227@xxxxxxxxxxxxxxxxxxxxxxx>
Organization: Aconex
References: <1180062348.6273.575.camel@edge> <Pine.SGI.4.58.0705251335430.101649415@xxxxxxxxxxxxxxxxxxxxxxx> <1180066020.6273.593.camel@edge> <Pine.SGI.4.58.0707041636040.10924227@xxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: nscott@xxxxxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
On Wed, 2007-07-04 at 17:15 +1000, Michael Newton wrote:
> 
> mail, i see ivan asked a similar qn. We should probably pursue this
> but it
> means a change in linuxmeister/build/init_buildsystem  -- which is
> actually part of SuSE's build stuff. There is no current facility for
> passing in --noscripts specifically, nor extra args in general. 

You may be able to override the definition of rpm itself (is it called
via a macro?) - to be RPM="rpm --noscripts" ... hard to say without
seeing the scripts though.

> 2 possible stopgaps:
> * restore the fallback to killall in oss, but not mangrove

If that route were taken, theres no need for pmcd.pid anymore, it should
all just be backed out.  Not sure I'd favor that though, its painful to
maintain a separate patch, and effectively reduces testing coverage from
both sides of the mangrove/oss fence.

> * have pmcd log creation of the pidfile. Only call killall if there is
>   a log file and it does *not* show creation of the pid file.

That'd probably work, I guess.  Just looking at that other patch you
sent out now, which looks like a third option... (doesn't seem to do
either of the above things afaict).

cheers.

--
Nathan


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