I've seen SIGPIPE from cfexecd from time to time, but not from
cfservd. It's usually, in my experience, and from what I've seen on
the cfengine mailing list, due to configuration errors. I agree that
a configuration error should not cause the daemon to crash, and it's
therefore a bug, but you should switch on the runtime debugging with -
d2 as a command line option to cfservd, which should help you
discover what's going on (and the same option will help the second
poster here, whose problem sounds like a different one to me, just
use it on cfagent rather than cfservd)
I think SIGPIPE tends to happen when cfengine is spawning a task to
do something, but a configuration error causes that subtask to exit
unexpectedly.
Tim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
