Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 231326 - syslog should only log in its own timezone (ignore local client timezone)
Summary: syslog should only log in its own timezone (ignore local client timezone)
Alias: None
Product: Fedora
Classification: Fedora
Component: sysklogd
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Peter Vrabec
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-07 19:07 UTC by Matthew Miller
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-03-12 09:02:19 UTC

Attachments (Terms of Use)

Description Matthew Miller 2007-03-07 19:07:19 UTC
Description of problem:

Currently, syslog follows the timezone setting of whatever program is doing the
logging. Thus, programs which happen to run in UTC or some other timezone appear
to log odd times (the actual zone used is never recorded in the log file). 

Perhaps worse, I can log with an almost arbitrary timestamp if I so choose:

TZ="UTC+23:56" logger "Look! I'm logging from yesterday!"

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. set TZ to anything you like
2. log a message
3. look in the appropriate log file
Actual results:

Time logged in the timezone you specified, but without saying so.

Expected results:

Time logged in the timezone under which syslogd is running.

Additional info:

There is a patch for this in the unreleased-for-years-and-years syslog 1.4.2. I
think we should backport this into Fedora. See:;r2=1.44;f=h

Comment 1 Nicolas Mailhot 2007-03-07 20:34:43 UTC
will this display timestamps in a sane datetime format like ISO 8601 ?

Comment 2 Matthew Miller 2007-03-07 20:40:54 UTC
No, it doesn't change the file format at all. It just consistently makes syslog
use the timezone it is running under rather than the timezone of the logging client.

While it'd be nice if syslog would use a better date/format, changing the format
of log files would be a fairly major undertaking and would need to be done with
a lot of care.

Comment 3 Matthew Miller 2007-03-08 19:27:38 UTC
Here's an example of the practical implication of this: bug #203671.

Comment 4 Peter Vrabec 2007-03-12 09:02:19 UTC
fixed in sysklogd-1.4.2-2.fc7

Comment 5 Matthew Miller 2007-03-12 12:05:11 UTC
Looks like this was already done by the time I filed it, huh? Thanks for the
psychic bug fix. :)

Note You need to log in before you can comment on or make changes to this bug.