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

[Tod Oace]

On Oct 5, 2004, at 14:20, Tom Carlile wrote:

> 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,

My yucky work-around:

filters:
        { started_over_two_hours_ago
                FromSTime:      "date(1970,1,1,0,0,0)"
                ToSTime:        "tminus(0,0,0,2,0,0)"
                Result:         "STime"
        }

processes:
        # Terminate any stale cfengine processes:
        any:: "cfagent" filter=started_over_two_hours_ago signal=term
        master:: "cfrun" filter=started_over_two_hours_ago signal=term

--
Tod Oace, Intel Corporation <tod@intel.com>