Opened 18 years ago
Last modified 16 years ago
#334 closed Enhancement
Specify time zone — at Version 4
Reported by: | Didactylos | Owned by: | davea |
---|---|---|---|
Priority: | Trivial | Milestone: | 6.0 |
Component: | Client - Logging | Version: | |
Keywords: | timezone UTC GMT messages | Cc: |
Description (last modified by )
It would be useful for troubleshooting to have the absolute time when events occurred. So, could the log include the timezone offset when giving the date?
(Suggested by JmBoullier)
Change History (4)
comment:1 Changed 18 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 18 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
That's a partial solution, but it doesn't help when people copy messages from the middle of the log.
When was this done? I can't find a timezone in any of my logs, and I built 5.11.0 on Monday.
comment:3 Changed 18 years ago by
An extra complication: the way I read it, the timezone stored in host_info can't be used as a message time offset, since it is the local standard time, not the actual local time. Basically, it ignores daylight saving. Possibly I'm reading it wrong; I didn't check this very carefully.
comment:4 Changed 18 years ago by
Description: | modified (diff) |
---|---|
Keywords: | timezone messages added; Timezone removed |
I have suggested to provide two logs: a computer-readable log, with non-changing format, and a user-readable log. Advantages: 3rd party tools would get more useful information than they can currently get from the existing log. We can do things to the user-readable log like changing messages for clarification or allowing translations, without breaking other programs.
Related to this ticket: the computer-readable log could save timestamps in UTC.
Done; time zone is given once, at start of message log