I am using the following for my config file. I have been told that you can sync a tcp connection to a certain number of lines, and I thought this was how you do it, but it dies on the first line that has the sync with a parse error. If I move it to its own line, outside of the tcp, it dies parsing there. Can someone please tell me where I am messing up here? Thanks, Matthew M. Copeland options { long_hostnames(off); log_fifo_size(1440000); }; source src { unix-stream("/dev/log"); internal(); }; destination normal_messages { tcp("129.235.66.4" port(999) sync(10)); }; destination immediate_messages { tcp("129.235.66.4" port(999) sync(0)); }; filter f_gs_alert { match("GS_ALERT"); }; log { source (src); filter(f_gs_alert); destination(immediate_messages); }; log { source(src); filter(DEFAULT); destination(normal_messages); }; _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
-----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-----
matthew.copeland@honeywell.com on Fri 23/02 18:00 +0000:
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?
glibc doesn't leak, that I've noticed. Syslog-ng uses a mark/sweep garbage collecting allocation backend, I think.
glibc doesn't leak, that I've noticed.
Syslog-ng uses a mark/sweep garbage collecting allocation backend, I think.
hmm.. Does anyone know how often the garbage collecter frees up the memory it has allocated? Matthew M. Copeland
matthew.copeland@honeywell.com on Fri 23/02 20:50 +0000:
glibc doesn't leak, that I've noticed.
Syslog-ng uses a mark/sweep garbage collecting allocation backend, I think.
hmm.. Does anyone know how often the garbage collecter frees up the memory it has allocated?
Have you considered reading the source? It's not too hard to follow or very large.
participants (2)
-
matthew.copeland@honeywell.com
-
Scott McDermott