30 May
2008
30 May
'08
1:46 p.m.
OK. As Bazsi suggested the flush_timeout() option enforces to write the
it doing nothing In fact syslog-ng sending to server only on restart, sometimes. Or with intervals in few hours this is my config on client: http://80.93.122.37/media/syslog-ng.conf and this is on server: http://80.93.122.37/media/syslog-ng.conf_srv
buffered logs to destinations. It would be useful having tcpdump/ ethereal running on the sending host during your test. This way you can compare the timestamp of the log message and the timestamp of the network packet to see whether there is a network latency.
tcpdump shows nothing. syslog-ng sending nothing