Changes between Initial Version and Version 1 of Ticket #23677


Ignore:
Timestamp:
Sep 27, 2017, 7:34:10 PM (2 years ago)
Author:
pastly
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #23677 – Description

    initial v1  
    1 Many issues come from incorrect time/date/timezone settings. And not all the time does Tor log about how it believes the user's clock is wrong but X hours and Y minutes.
     1Many issues come from incorrect time/date/timezone settings. And not all the time does Tor log about how it believes the user's clock is wrong by X hours and Y minutes.
    22
    33For many linux/macos users we can ask them to tell us the output of `date -u` as a huge troubleshooting help. But not everyone is capable of that. A maybe shouldn't be expected to be.
     
    771. Log what Tor thinks the UTC time, local time, and configured timezone are at startup once
    88
    9 2. Log periodically (say, every HeartbeatPeriod) what Tor thinks[... all the above ...]
     92. Log periodically (say, every HeartbeatPeriod) what Tor thinks [... all the above ...]
    1010
    1111Bonus idea:
    1212
    13 Can we put the timezone in the log line's time stamp? Would that be enough? Is that dangerous for users? Do we make promises about parse-ability that we'd be breaking?
     13Can we put the timezone in the log line's timestamp? Would that be enough? Is that dangerous for users? Do we make promises about parse-ability that we'd be breaking?
    1414