Description of problem: uncatched error if pid file does not exist on stop Version-Release number of selected component (if applicable): syslog-ng-2.1.4-1.el5 How reproducible: Always Steps to Reproduce: # /etc/init.d/syslog-ng stop Stopping syslog-ng: [ OK ] # /etc/init.d/syslog-ng restart Stopping syslog-ng: /etc/init.d/syslog-ng: line 70: /var/run/syslog-ng.pid: No such file or directory /etc/init.d/syslog-ng: line 70: /var/run/syslogd.pid: No such file or directory [FAILED] Starting syslog-ng: [ OK ] Actual results: see above Expected results: Not such strange error message Additional info:
Commited this patch[1] to devel/ which I believe will solve the issue. However, I was unable to build the package for EL-5 due to some linking errors against libnet. Will have to resolve this first. [1] http://cvs.fedora.redhat.com/viewvc/rpms/syslog-ng/devel/syslog-ng.init.d?r1=1.1&r2=1.2
Closing this ticket as the problem appears to have been fixed in syslog-ng-2.1.4-3. Please feel free to re-open this ticket if the problem still persist. Specfile changelog: ... * Tue Aug 18 2009 Ray Van Dolson <rayvd> - 2.1.4-3 - Init script fix (bug#517339) ... /jpo