Incidentally, as a work around you can simply get cf-agent to restart cf-execd once a week or once per day for that matter.
M Francoeur, Louis wrote: > After installing 3.0.4, we let cfengine run for almost 24 hours > and it looks like we still have a memory leak. > > Wed Mar 10 14:13:13 EST 2010 > 2076K cf-execd > > Thu Mar 11 13:04:28 EST 2010 > 4508K cf-execd > > Louis > -----Original Message----- > From: help-cfengine-boun...@cfengine.org > [mailto:help-cfengine-boun...@cfengine.org] On Behalf Of Mark Burgess > Sent: Tuesday, March 09, 2010 2:50 PM > To: Lebel, Marco > Cc: help-cfengine@cfengine.org > Subject: Re: cf-execd & cf-monitord - Memory leaks? > > > Yes, try upgrading > > Lebel, Marco wrote: >> Hello all, >> >> >> >> Is there a known bug with the community version 3.0.2 for a memory leak >> of any sorts? >> >> >> >> I do not have all of the details but when I start cf-execd (daemon mode) >> it uses close to 3M of memory on my servers and after some two weeks it >> shots up to 322M!!!! To me it looks like a memory leak but then again I >> have been known to be wrong. >> >> >> >> Thanks in advance, >> >> >> >> Marco >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Help-cfengine mailing list >> Help-cfengine@cfengine.org >> https://cfengine.org/mailman/listinfo/help-cfengine > -- Mark Burgess ------------------------------------------------- Professor of Network and System Administration Oslo University College, Norway Personal Web: http://www.iu.hio.no/~mark Office Telf : +47 22453272 ------------------------------------------------- _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
