[syslog-ng]Memory usage and reclaiming memory

[matthew.copeland@honeywell.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


When syslog-ng gets a disconnect from the network and starts spooling up
messages, I noticed that when I reconnected it to the network, and after
it had spooled all the messages to the remote logging server, that the
client syslog-ng process was still taking up the memory that it had
allocated.  Running under Linux.  Does syslog-ng keep the memory
allocated in some page table or list, or is libc the culprit in not
releasing memory that processes aren't using anymore? 

Matthew M. Copeland
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iD8DBQE6lqVCBVcI9mVTMk8RAiLSAKCwPz8HJkBH5Wl695L8nsUg2f6dTQCg7bS/
tzvUZInEjodqUZ1hGQqjJ68=
=hi4O
-----END PGP SIGNATURE-----