[syslog-ng]problem on HPUX with s_tcp snd d_tcp

[Loic Minier]

Stephan Hendl <Stephan.Hendl@lds.brandenburg.de> - Thu, Jul 01, 2004:

> It seems to me that the state 'FIN_WAIT_2' doesn't allow the hpux
> syslog-ng to accept data from the linux clients and this state is quite
> very long. 

 I could not reproduce this on my Linux 2.6 system:
 - I killed syslog-ng with SIGTERM, SIGINT, SIGKILL, and SIGHUP while a
   telnet connection was open to the TCP port;
 - I restarted syslog-ng as soon as it was dead, and telneted
   successfully to the same port again, and syslog-ng saw my connection.

 Could it be a problem on the client side?  My TCP connection gets
 closed when I kill -HUP syslog-ng.

 Or could it be a socket(7) option missing on the listening TCP socket?
 I do a setsockopt with SO_REUSEADDR on my sockets prior to binding
 them, which does not seem to be in syslog-ng.

-- 
Loïc Minier <lool@dooz.org>