pcp
[Top] [All Lists]

Re: [pcp] qa/518 tweaks on pcpfans.git fche/dev

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] qa/518 tweaks on pcpfans.git fche/dev
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 4 Nov 2014 18:55:29 -0500 (EST)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <001701cff60f$ff53d460$fdfb7d20$@internode.on.net>
References: <20141031201304.GE1913@xxxxxxxxxx> <002c01cff56c$6febc830$4fc35890$@internode.on.net> <20141101010427.GF1913@xxxxxxxxxx> <001701cff60f$ff53d460$fdfb7d20$@internode.on.net>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: AQIWIQMIOeKcOGylRqOgmw6wi16M5QIkql93Aj2/Pb+bnMRKEG114gej
Thread-topic: qa/518 tweaks on pcpfans.git fche/dev
Hi Ken,

----- Original Message -----
> [...]
> 3. Frank's observations about pmie and signals is a bit concerning, although
> I see evidence of "try TERM and if that does not work try KILL and repeat
> until successful or timeout" in the pmie init script, so perhaps this is a
> long standing problem that has been masked by hackery.  pmie does have a
> TERM signal handler and a delayed exit but only after the nanosleep() ... so
> if we are blocked somewhere else, or don't abandon expression evaluation
> completely when an I/O returns with EINTR then we could be off in the weeds
> long enough for some script to believe pmie has not died.
> 
> Any insight into 3. would be helpful.

The pmie (init/check) scripts were initially close cousins to the pmlogger
scripts - the sigterm-upgrade-to-sigkill there is very likely to be mainly
for historical reasons, rather than tackling any pmie specific issue.

cheers.

--
Nathan

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