#334 closed Enhancement (fixed)
Specify time zone
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 (12)
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.
comment:5 Changed 18 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
The change is in the SVN trunk, and will appear in the next release.
The local time used by BOINC takes daylight savings into account (if not, that's a bug; please report separately).
It would take too much space to include TZ offset in each message line, and it would confuse users to report times in UTC. So I'm going to leave it as is.
comment:7 Changed 18 years ago by
(In [13293]) - client: timezone reflects daylight savings time (Win)
from David Barnard; fixes #334
- GUI RPC: add <success/> replies for ops that don't return anything
- GUI RPC: check args for project_attach
- GUI RPC: return error (not blank) if no prefs override file
- add error string for ERR_TOO_MANY_EXITS
comment:8 Changed 17 years ago by
(In [13879]) - client: timezone reflects daylight savings time (Win)
from David Barnard; fixes #334
- GUI RPC: add <success/> replies for ops that don't return anything
- GUI RPC: check args for project_attach
- GUI RPC: return error (not blank) if no prefs override file
- add error string for ERR_TOO_MANY_EXITS
client/
gui_rpc_server_ops.C hostinfo_win.C
lib/
str_util.C
comment:9 Changed 17 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
I'm not so sure it now works in BOINC 5.10.24 .. With DST on here in The Netherlands I'm at UTC+2, but BOINC continues to tell me I'm at UTC+1.
Local time is UTC +1 hours |
Windows clock says I live at W. Europe Daylight Time
comment:11 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Ah, I see. In 13904
Done; time zone is given once, at start of message log