Ticket #334 (closed Enhancement: fixed)

Opened 1 year ago

Last modified 11 months ago

Specify time zone

Reported by: Didactylos Assigned to: davea
Priority: Trivial Milestone: 6.0
Component: Client - Logging Version:
Keywords: timezone UTC GMT messages Cc:

Description (Last modified by Nicolas)

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

07/13/07 08:40:43 changed by davea

  • status changed from new to closed.
  • resolution set to fixed.

Done; time zone is given once, at start of message log

07/13/07 08:51:16 changed by Didactylos

  • status changed from closed to reopened.
  • resolution deleted.

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.

07/13/07 09:28:15 changed by Didactylos

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.

07/13/07 09:52:22 changed by Nicolas

  • keywords changed from Timezone UTC GMT to timezone UTC GMT messages.
  • description changed.

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.

07/13/07 10:36:03 changed by davea

  • status changed from reopened to closed.
  • resolution set to fixed.

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.

07/14/07 13:28:29 changed by Nicolas

r13155 seems to have further changes about this.

08/10/07 09:02:11 changed by davea

(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

10/17/07 11:44:53 changed by romw

(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

10/18/07 10:21:20 changed by Ageless

  • status changed from closed to reopened.
  • resolution deleted.

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.

18-Oct-07 12:39:04 Local time is UTC +1 hours

Windows clock says I live at W. Europe Daylight Time

10/18/07 10:30:15 changed by Didactylos

David has fixed this already.

10/18/07 10:35:15 changed by Ageless

  • status changed from reopened to closed.
  • resolution set to fixed.

Ah, I see. In 13904

10/18/07 10:35:33 changed by Ageless

Sorry, overlooked that due to that spammer being busy again.

If this page is incomplete or incorrect, please edit it or add it to the wiki to-do list. To do this, you must be logged in; click Login or Register above.