We have the same comportement. It *appears* that building from the source leads to a binary that leaks less than the one provided in the official package (if I remember well, the only differences are the version of libpcre, libdb and libdl, as well as libpromises which is not linked in the same way), but I'm not enough of a sysadmin to be sure of that
Nicolas CHARLES Normation SAS - http://www.normation.com 44 rue Cauchy – 94110 ARCUEIL +33 (0)1 83 62 26 96 - +33 (0)6 14 63 25 18 On 22/12/2010 21:09, no-re...@cfengine.com wrote: > Forum: Cfengine Help > Subject: Re: Cfengine Help: cf-serverd memory leak still (v3.1.2) > Author: matter > Link to topic: https://cfengine.com/forum/read.php?3,19854,19902#msg-19902 > > I have been doing some tests as well. I have the latest BerkeleyDB statically > compiled and slimed down. Same with openssl. cf-execd behaves extremely well. > I don't see any leakage there. cf-serverd does well, it seems to grow for a > day, but then it seems some garbage collection happens, and slims down on > memory usage. There is very slow growth there. cf-monitord, on the other > hand, grows fairly quickly and steadily. > > I am compiling all this with native AIX compiler. I am still no closer in > tracking down what is actually happening. > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
