Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu

[Andrew Stribblehill]

Quoting Tom Carlile <tcarlile@dmotorworks.com> (2004-10-05 22:20:32 BST):
> This is not only specific to Debian.  I have seen this same behavior on
> Redhat AS2.1 and ES3 hosts.  Yes it is burning cpu writing to closed
> pipes.  Any hope of a fix making it into the main cfengine?  Thanks, 
> 
> On Tue, 2004-10-05 at 06:25, Andrew Stribblehill wrote:
> > Quoting Will Lowe <harpo@thebackrow.net> (2004-10-05 03:50:29 BST):
> > > I've got a few machines running 2.1.10.  They're running cfexecd via
> > > cron as "/usr/sbin/cfexecd -F".
> > > 
> > > There's an error in my config that doesn't appear when I run cfagent
> > > by hand, but does when cfexecd calls it as
> > > "/var/lib/cfengine2/bin/cfagent -Q
> > > smtpserver,smtpfrom,sysadm,fqhost,ipaddress,EmailMaxLines,schedule":
> > > 
> > > 
> > > cf:cfengine:foo:/etc/cfengine/debian.conf:193: sysadm undefined variable 
> > > 
> > > The result is that cfexecd calls FatalError and exit()s, leaving
> > > cfagent still running, burning lots of cpu (probably due to writes on
> > > closed pipes). Cfexed should probably kill off the child cfagent
> > > process?
> > 
> > This is a bug specific to Debian, fixed in the latest release
> > (2.1.10-1.1). Sorry about that. For more information about the bugs,
> > look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=271735 and
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272822.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272822#msg20 has the
patch needed to disable SIGPIPE from the SIGPIPE handler :) I think
it should be applied upstream. Mark, what do you think?

-- 
FAIR ISLE
NORTHERLY 6 TO GALE 8, BUT CYCLONIC 5 OR 6 IN EAST AT FIRST. SHOWERS.
MAINLY GOOD