On Mon, Jun 26, 2000 at 08:42:34AM -0400, Scott McDermott wrote:
I noticed your post on the syslog-ng archives concerning memory leaks in the software. I was wondering if you had met any success reports with this patch. I just discovered my DMZ loghost has a 70MB syslog-ng image in core after running only a couple of weeks; there is most *definitely* a memory leak. I was going to track it down myself, but thought I would check the list archives first...indeed, your patch was posted.
Before I implement the patch, I was wondering if you've had success running some syslog-ngs for more than a week, with at least half a dozen hosts logging to it, and kept the memory image within reasonable limits, with this patch. If it's not a complete leak preventer, I'd just as soon do a full audit of the source, since I simply must use syslog-ng in production. Either that, or we could split the work or something...
That patch fixed some leak bugs, but as it seems not all of them. I'm now trying to reproduce the problem. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt