I'm receiving thousands of syslogs per second, so the truss is not that useful - it's too difficule to isolate the interval. When failed HUP issue occurrs, no log entry is written to syslog, and the daemon continues running normally. When a successful HUP occurs, the appropriate message appears in syslog. I did not have this issue when I was testing, only when I put the server under extreme load, so that be a prerequisite for the issue to occur. Peter -----Original Message----- From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu]On Behalf Of Balazs Scheidler Sent: Thursday, May 06, 2004 12:59 PM To: syslog-ng@lists.balabit.hu Subject: RE: [syslog-ng]Problem with "kill -HUP" on syslog-ng 2004-05-06, cs keltezéssel 18:39-kor Wyner, Peter ezt írta:

I have had similar issues HUPing 1.6.2 under Solaris 2.8. My resolution is to kill have the script kill -9 the process and start a new one instead of HUPing. The behavior is not consistant - sometimes it will honor the SIGHUP and sometimes it won't.

can you be more specific? it simply does nothing, it crashes or? syslog-ng should send this message to the system log when it receives a system log: notice("SIGHUP received, restarting syslog-ng\n") do you receive this message when it does not correctly restart? can you attach truss to the running syslog-ng process when you send a HUP signal to it? -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html