Actually, I ran it with nisplus for a while but it has been some time ago. I didn't have any problems with syslog-ng in connection to nisplus but we had enough problems with nisplus to eventually wind up going back to nis. I have used nis for over a year and don't have any problems using it with syslog-ng. Problems with nisplus would not be surprising. Regards, Drew -----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Sent: Thursday, August 02, 2001 7:48 PM To: Craig J Constantine Cc: syslog-ng@lists.balabit.hu Subject: [syslog-ng]Re: syslog-ng's memory footprint growing constantly On Thu, Aug 02, 2001 at 12:05:29PM -0400, Craig J Constantine wrote:
...on 8/2/01 11:19 AM, the following was received from bazsi@balabit.hu
ok, we have some kind of string leak. what does "hosts.org_dir" in your environment mean? is it a directory which syslog-ng creates, or a filename? or some part of some message?
I have no idea. :) That string isn't in my syslog-ng config, nor *anywhere* in the syslogs recorded by syslog-ng today, nor even anywhere in the syslog-ng distribution. Might be just a lot over strings overlayed in memory... very weird.
I found hosts.org_dir, it's in the file /lib/libnss_nisplus.so, so I assume you are using nisplus. syslog-ng resolves a lot of hostnames, isn't it possible that nisplus is leaking somewhere? I've never ran syslog-ng with a computer using nisplus, that might be an explanation why others didn't encounter this bug. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng