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. 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:01 PM To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng]Problem with "kill -HUP" on syslog-ng 2004-05-06, cs keltezéssel 13:16-kor Stephane OMNES ezt írta:

Hi, I need some help because I encountered a problem when trying to make some automatic logrotate script with syslog-ng. My "logrotate script" is the following : /var/log/*.log { sharedscripts postrotate /bin/kill -HUP `cat /var/run/syslog-ng.pid 2> /dev/null` 2> /dev/null || true endscript }

The syslog-ng daemon never restarts when you type "kill -HUP <syslog-ng.pid>" I tried also "kill -SIGUP ..." same result (the daemon is stopped but never restarts...). Did someone ever encountered this problem ? Is there any "proper" solution ?

I'm currently workin under RedHat Enterprise v3.0

I don't know any problems wrt reload in syslog-ng 1.6.x, are you really sure you are HUPing the correct PID? -- 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