All, I am running into an issue on a previously working syslog_ng 1.6.2 server. There were no configuration changes between when it worked and now (when it doesn't). The syslog sever will process a large number of packets for a period of time and then suddenly the processor utilization goes down to zero, files stop being written, and truss shows: door_call(6, 0xFFBED340) (sleeping...) signotifywait() (sleeping...) lwp_sema_wait(0xFEF0DE60) (sleeping...) I am collecting syslog on a high udp port: # # Syslog-ng example configuration file for Solaris # # Copyright (c) 1999 Balazs Scheidler # $Id: syslog-ng.conf.solaris,v 1.2 1999/11/15 12:30:41 bazsi Exp $ # # Solaris 2.5.1 and below uses the STREAMS driver, above extends it # with doors. For 2.5.1 remove the door() option from the source declaration. # options { log_fifo_size(1024); sync(0); dns_cache(yes); dns_cache_expire(60); use_dns(yes); chain_hostnames(no); keep_hostname(no); }; source local { sun-streams("/dev/log"); internal(); }; source std_udp { udp( port(52001) ); }; destination all { file("/var/log/messages"); }; destination dst1 { file("/syslog/dst1/current/$HOST" dir_perm(0755) perm(0644)); }; log { source(local); destination(all); }; log { source(std_udp); destination(dst1); }; Any ideas? Thanks, Peter