On Fri, 25 May 2007, Nathan Scott wrote:
> 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
[..the famous serial killer..]
> 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?
this rang a bell, so now i finally had a minute to check back thru the
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.
Mark do you know how to go about getting such a change into linuxmeister?
Or recommend me someone to talk to? Im assuming we cant just change it in
our own copy? (in addition of course to suggesting same to SuSE)
2 possible stopgaps:
* restore the fallback to killall in oss, but not mangrove
* 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.