Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12469 - Avahi uses GMT instead of local time in logs.exit
Attached to Project:
Arch Linux
Opened by Chris (chris256) - Tuesday, 16 December 2008, 02:41 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 27 December 2008, 14:09 GMT
Opened by Chris (chris256) - Tuesday, 16 December 2008, 02:41 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 27 December 2008, 14:09 GMT
|
DetailsAvahi uses GMT time stamps in logs.
The version I am using is 0.6.23-2. |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Saturday, 27 December 2008, 14:09 GMT
Reason for closing: Not a bug
Saturday, 27 December 2008, 14:09 GMT
Reason for closing: Not a bug
Comment by Chris (chris256) -
Tuesday, 16 December 2008, 02:52 GMT
Please ignore the "exit" at the end of the summary. Somebody interrupted me while I was writing this and I accidentally submitted it like that prematurely. I don't know how to edit submissions. I meant to include the following information. I believe the page http://avahi.org/ticket/221 explains what is happening. The logs effected for me are: daemon.log, everything.log, and messages.log.
Comment by Glenn Matthys (RedShift) -
Tuesday, 16 December 2008, 10:02 GMT
Did you use the solution that was provided by the upstream bugreport?
Comment by Chris (chris256) -
Saturday, 20 December 2008, 01:36 GMT
I did implement the solution provided by the upstream bugreport and it does fix the problem. I copied /etc/localtime to /etc/avahi/etc/localtime. Avahi now puts the correct timestamp in my logs.