syslog-ng exits when system time set backwards
Hello, I've googled the mailing list, but could find any related threads. On FreeBSD, syslog-ng 1.6.8 exits when the system time is set to a value earlier than the previous value. Has anyone else encountered this before? Is there a fix or a configuration issue? $ ps auxwww | grep syslog-ng root 1040 0.0 0.1 1516 1208 ?? Ss 10:15AM 0:00.08 /usr/local/sbin/syslog-ng kstepanchuk 6529 0.0 0.0 1568 980 p0 R+ 10:38AM 0:00.00 grep syslog-ng $ sudo date 200501010000 Sat Jan 1 00:00:00 EST 2005 $ ps auxwww | grep syslog-ng mfeeney 6533 0.0 0.0 1612 996 p0 S+ 12:00AM 0:00.00 grep syslog-ng Thanks,
On Fri, 2009-08-07 at 15:31 -0400, Kirill Stepanchuk wrote:
Hello,
I’ve googled the mailing list, but could find any related threads. On FreeBSD, syslog-ng 1.6.8 exits when the system time is set to a value earlier than the previous value.
Has anyone else encountered this before? Is there a fix or a configuration issue?
$ ps auxwww | grep syslog-ng
root 1040 0.0 0.1 1516 1208 ?? Ss 10:15AM 0:00.08 /usr/local/sbin/syslog-ng
kstepanchuk 6529 0.0 0.0 1568 980 p0 R+ 10:38AM 0:00.00 grep syslog-ng
$ sudo date 200501010000
Sat Jan 1 00:00:00 EST 2005
$ ps auxwww | grep syslog-ng
mfeeney 6533 0.0 0.0 1612 996 p0 S+ 12:00AM 0:00.00 grep syslog-ng
well, syslog-ng 1.6.8 is ancient history, you should be using 3.0 instead. For what it's worth: I don't know why it exits though. Can you -- Bazsi
participants (2)
-
Balazs Scheidler
-
Kirill Stepanchuk