That is the complete configuration file. I just built the server last week. It is not in production yet, that is why the configuration file is so small. Only my desktop is sending log messages to it, so traffic is minimal. When I remove the internal section; the program behaves as I would expect. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Thursday, April 05, 2007 12:20 PM To: Syslog-ng users' and developers' mailing list Subject: RE: [syslog-ng] Syslog-ng version 2.0.3 memory problems On Thu, 2007-04-05 at 08:54 -0400, James Long wrote:
Thanks Bazsi, Interesting suggestion. The configuration I'm using is pretty bland. I removed the internal section on the source line below and it appears to have fixed the problem. I'm guessing the proper configuration would be to have two different sources, use the same destination and then use two different log lines.
source net { udp(ip(0.0.0.0) port(514)); }; internal(); };
destination hosts { file("/$HOST/$FACILITY" owner("syslogng") group("syslogng") perm(0640) dir_perm(0750) create_dirs(yes)); };
log { source(net); destination (hosts); };
Thank again, I appreciate the quick response.
hmm.. the internal() source should work in the configuration snippet that you posted. is it the complete configuration file, or you have other log statements? -- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html