Hi, looks like a bug, can't be a feature... I have defined a remote destination like: destination d_remotelog { udp( "192.168.1.1" port(514) ) ;}; And use it like log { source(s_local); filter(f_emerg); destination(d_all); destination(d_remotelog); }; Today, I've rebooted "remotelog" host, and detect, that the syslog-ng daemon on the other box dies without any "die now" notice. Last log entries: Feb 28 09:12:38 host syslog-ng[28338]: STATS: dropped 0 Feb 28 09:19:47 host syslog-ng[28338]: Connection broken to AF_INET(192.168.1.1.50:514), reopening in 60 seconds Looks like it dies short after this time, because a running mailman-2.0.x cron job stops logging, too: cron-200302:Feb 28 09:18:01 host CROND[368]: (mailman) CMD (/usr/bin/python -S /var/mailman/cron/qrunner) cron-200302:Feb 28 09:19:00 host CROND[388]: (root) CMD (/usr/local/sbin/AVP_update_bases.pl) cron-200302:Feb 28 09:19:00 host CROND[389]: (mailman) CMD (/usr/bin/python -S /var/mailman/cron/qrunner) cron-200302:Feb 28 09:20:01 host CROND[407]: (root) CMD (/usr/local/sbin/ipacc-get tmplog) cron-200302:Feb 28 09:20:01 host CROND[408]: (root) CMD (/usr/lib/sa/sa1 1 1) cron-200302:Feb 28 09:20:01 host CROND[409]: (mailman) CMD (/usr/bin/python -S /var/mailman/cron/qrunner) cron-200302:Feb 28 09:20:01 host CROND[410]: (mailman) CMD (/usr/bin/python -S /var/mailman/cron/gate_news) cron-200302:Feb 28 09:21:00 host CROND[450]: (mailman) CMD (/usr/bin/python -S /var/mailman/cron/qrunner) [ no further lines :-( ] Nothing else was logged except this 5 cron lines, checked by # grep "Feb 28 09:2" * |more BTW (hopefully off-topic): "host" is IPv6 enabled in general. Runned kernel: RHL 2.4.18-18.7.x with OpenWall patch Hopefully someone can help me. Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/