You´re right, I was confusing tcp-keep-alive option with keep-alive, since tcp-keep-alive didn't work in my syslog-1.6.2 I thought you meant the keep-alive option. I compiled the last version and now the option works and my problem is solved, thank you very much. Francisco -----Original Message----- From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu]On Behalf Of Balazs Scheidler Sent: Martes, 28 de Diciembre de 2004 03:17 p.m. To: syslog-ng@lists.balabit.hu Subject: RE: [syslog-ng]Problem with TCP connection not timing out On Tue, 2004-12-28 at 10:35 -0300, ARGEXT-HIDALGO, FRANCISCO wrote:

Thanks for the response, I'll test it now, but the documentation says that this is the default behaviour, so I'm not sure if this will change anything. On the other hand, shouldn't the OS drop these connections?, some of them have days there, and this monday, there where almost 40 dead connections that where "ESTABLISHED".

I'm sorry but no, the OS does not reap these connections. Some application layer timeout could solve the issue, though at the same time it might also cause other problems like message drops. Where did you read that it was default? <row> <entry>tcp-keep-alive()</entry> <entry>yes or no</entry> <entry> Available for tcp() only, and specifies whether to enable TCP keep alive messages using the SO_KEEPALIVE socket option. </entry> <entry>no</entry> </row> Nevertheless looking at the source it seems not to be enabled by default. But if you tell me a reference I'll fix the documentation. -- 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