RE: cfservd thrushes, nodes fail to get anything

[Luke Youngblood]

It's impossible to predict what will happen when applications run out of
memory and swap due to /tmp filling up.  This is what most people would call
a case of "operator error".  It might be useful to have a cfagent --cleanup
option that would cleanup any temp databases that might be out there, but I
don't think software can realistically be expected to do much of anything
once memory and swap has been exhausted.

Luke

-----Original Message-----
From: help-cfengine-bounces+lyoungblood=phonechargeinc.com@gnu.org
[mailto:help-cfengine-bounces+lyoungblood=phonechargeinc.com@gnu.org] On
Behalf Of Mark Burgess
Sent: Wednesday, May 25, 2005 6:14 AM
To: Yaroslav Halchenko
Cc: help-cfengine@gnu.org
Subject: Re: cfservd thrushes, nodes fail to get anything

I cannot see how this can occur. Any ideas from anyone else. There are
no loops. It is possible that this is internal to db.

Mark

On Sat, 2005-05-07 at 18:41 -0400, Yaroslav Halchenko wrote:
> I've found the reason and probably that would be benefitial to adjust
> cfservd to don't get into such situation again:
> 
> I had a leftover file 
> /tmp/__db.testDATABASEcache
> 
> so strace revealed me infinite loop of
<snip>