These are the last two lines in the log after restarting syslog-ng: Nov 29 12:49:15 src@xxxx syslog-ng[5120]: syslog-ng version 1.5.23 going down Nov 29 12:49:16 src@xxxx syslog-ng[5133]: syslog-ng version 1.5.23 starting But 'date' gives the following: Fri Nov 29 13:49:23 MET 2002 'date -u' gives the same time as the internal message. So messages coming from other sources are timestamped with local time, internal() messages are stamped with GMT. Why is that?
On Fri, Nov 29, 2002 at 02:02:26PM +0100, henriksa@telia.com wrote:
These are the last two lines in the log after restarting syslog-ng:
Nov 29 12:49:15 src@xxxx syslog-ng[5120]: syslog-ng version 1.5.23 going down Nov 29 12:49:16 src@xxxx syslog-ng[5133]: syslog-ng version 1.5.23 starting
But 'date' gives the following:
Fri Nov 29 13:49:23 MET 2002
'date -u' gives the same time as the internal message. So messages coming from other sources are timestamped with local time, internal() messages are stamped with GMT. Why is that?
chroot ? syslog-ng might not find /etc/localtime which is needed for time zone information. the value returned by localtime() is used. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
Is there a way to make syslog-ng use the month name instead of the month number when using $MONTH? Ja
participants (3)
-
Balazs Scheidler
-
henriksaļ¼ telia.com
-
Ja Wallaby