Thanks Bazsi and Ted, This is exactly the information I was looking for. I had tested with removing the cable, but there no way (that I could find) to reliably test a connection dropping out once it had been established. Thanks Phil Balazs Scheidler wrote:
2004-05-17, h keltezéssel 06:05-kor Philip Webster ezt írta:
Hello,
I'm wondering about the resilience of syslog-ng to TCP connection dropouts. I've tested what happens when there is no connection available - syslog-ng buffers the output and continues to write to local files, ie. it doesn't block.
But what happens if the TCP connection fails halfway through? So, for example, the three-way handshake has been completed, but there is no response after the first data packet is sent because the remote host (or router, switch, ISP ...) has stopped responding. I can't really test this, so does anyone know how syslog-ng handles it?
exactly the same, syslog-ng 1.6.x does never block. (or at least should not), there's no flow control.