-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Print human-readable timezone information #1981
Conversation
… this in the log files to not needlessly change for format. Open for discussion Signed-off-by: DL6ER <dl6er@dl6er.de>
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
1 similar comment
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Signed-off-by: DL6ER <dl6er@dl6er.de>
Conflicts have been resolved. |
I think this is a useful feature which should be used everywhere. v6 will break a lot of existing stuff, I think it's OK to change the log format. (I think to remember we already change the format from v5 to V6 by including message severity...) |
Signed-off-by: DL6ER <dl6er@dl6er.de>
@yubiuser The timezone is now always there |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2024-06-02 17:17:51.619 [46769M] INFO: Thread housekeeper (1) is idle, terminating it.
2024-06-02 17:17:51.619 [46769M] INFO: Thread DNS client (2) is idle, terminating it.
2024-06-02 17:17:51.619 [46769M] INFO: All threads joined
2024-06-02 17:17:51.623 [46769M] INFO: Stored 1 API session in the database
2024-06-02 17:17:52.820 [46769M] INFO: ########## FTL terminated after 19h 48m 55s (code 0)! ##########
2024-06-02 17:17:53.250 CEST [60185M] INFO: ########## FTL started on nanopi! ##########
2024-06-02 17:17:53.251 CEST [60185M] INFO: FTL branch: new/timezone
2024-06-02 17:17:53.252 CEST [60185M] INFO: FTL version: vDev-14ea246
2024-06-02 17:17:53.252 CEST [60185M] INFO: FTL commit: 14ea246f
What does this implement/fix?
Add timezone information in human-readable timestamps.
This change has been triggered by a user seeking help after they had found a mismatch of timestamps between their two Pi-holes. We have been able to track it down to one server using a local timezone and the other one having been set to UTC.
Old
New
Related issue or feature (if applicable): (private communication)
Pull request in docs with documentation (if applicable): N/A
By submitting this pull request, I confirm the following:
git rebase
)Checklist:
developmental
branch.