Hi Martins,
----- Original Message -----
> Nathan,
> On 1/29/2015 4:42 PM, Nathan Scott wrote:
> >> I sent that mail from the time warp that is labelled "it is OK for all
> >> PCP processes to run as root" ... later I realized that in the brave new
> >> world where running as root has become less fashionable this won't work
> >> if the PMDA needs root priveleges, because once pmcd is able to accept
> >> the SIGHUP it has downgraded itself to user "pcp" ... so restarting
> >> _pmcd_ (as root) is the only option in your case.
> >>
> > This is now fixable, happily. See point #2 here:
> > http://oss.sgi.com/archives/pcp/2014-06/msg00111.html
> > from "2. Restarting / Installing PMDAs", and:
> >
> > $ grep STARTPMDA src/include/pcp/pmda.h
> > /*#define PDUROOT_STARTPMDA_REQ 0x9007*/
> > /*#define PDUROOT_STARTPMDA 0x9008*/
> >
> > If anyone wants to hack on this, please send me a note - I have some
> > sample code that will help. It would be good to have this functionality
> > back; the building blocks are now in place (since pcp-3.10.2) and it'll
> > be an interesting little hacking project I think.
> This would be great to have. I won't have time to take this on for the
> next couple of weeks. I will ping you for the sample code then, unless
> someone else looks at it in the meantime.
>
Lukas ended up working on this and getting it all in for the last release
(pcp-3.11.0). As of today (so, next release) we have a pmie rule that'll
automate the restart of failed PMDAs by sighup'ing pmcd if you chkconfig
pmie on.
Works nicely here, and can restart PMDAs running under any user account now
that the above is all in place (and basically the same pmie rule to the one
we discussed in this thread - by default it will also log to syslog whenever
it kicks pmcd).
cheers.
--
Nathan
|