On Fri, 2007-05-25 at 13:45 +1000, Michael Newton wrote:
> On Fri, 25 May 2007, Nathan Scott wrote:
> > It looks like the pcp start script (src/pmcd/rc_pcp) has been
> > changed post pcp-2.5.x to use the file /var/run/pcp/pmcd.pid
> > for decisions about whether pmcd is running or not. Can you
> > send details about the problem being solved by this change?
>
> * rpm -e pcp<blah> stops pcp
> * kill by name means removing pcp in a chroot stops global pcp
> ..so make clean in mangrove would stop pcp on the build machine
Ah, now it makes more sense. Thanks.
Would changing the mangrove build to do "rpm -e pcp --noscripts"
resolve this and also allow the upgrade issue to be fixed?
> there was lots of discussion on this, and i think this was pretty much the
Could that discussion be made available to stop me having to
second guess everything y'all have already thought of? ;)
> only sensible-looking solution. I originally had a fallback to killall,
> which is what you seem to be proposing.. the problem with this being,
> as ivan pointed out, it doesnt solve the problem! ie the chroot stop
> will still kill the global pcp
cheers.
--
Nathan
|