Thanks for pointing me in the right direction Gordon, read your mail around the same time I was experiencing this issue, saved me some troubleshooting. Bazsi, your method of adding a -f to the start_daemon call also fixes this problem for me on debian. -Lance On Thu, Dec 3, 2009 at 9:01 AM, Balazs Scheidler <bazsi@balabit.hu> wrote:

Hi,

We have an alternative solution for the same problem, waiting for a release to happen.

Can you check if this one works for you too?

This adds a -f to the start_daemon call.

On Tue, 2009-12-01 at 14:57 -0800, Gordon McAllister wrote:

...

Hello,

I'm running the syslog-ng 3.0.4 RPM on CentOS 5.4 and came across a problem where syslog-ng would not start properly after an unclean shutdown, since the old PID file was still in place. Attached is a patch to the init script supplied with the RPM that attempts to correct this.

Regards, ---Gordon

______________________________________________________________________________

...

Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html

-- Bazsi

______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html

______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

-- Lance Laursen Demonware Systems Engineer 1-604-689-4594 x3702