Hi
I'm currently working with this crate and noticed, that in the log-files, it always prints UTC, instead of CEST (my local timezone).
Because of this, the logrotation of syslog-ng doesn't work correctly, since it's configured to use CEST.
So I've took a deep dive first in my program and when I couldn't find anything I checked this crate for matches of a hardcoded utc and found the following commit 839eb52.
The mentioned issue in the time crate time-rs/time#380, has been closed and to check if the now_local() function now works on unix-based systems, I've forked the crate, removed the "unix utc hardcode" part: VeldoraTheDragon@888ab04 and used it in my program, which then worked flawlessly.
Is there a possibility to remove it aswell, so unix-based systems can again use local-time?
The current solutions seems more like a workaround to me than a proper solution.
Thanks.
Hi
I'm currently working with this crate and noticed, that in the log-files, it always prints UTC, instead of CEST (my local timezone).
Because of this, the logrotation of syslog-ng doesn't work correctly, since it's configured to use CEST.
So I've took a deep dive first in my program and when I couldn't find anything I checked this crate for matches of a hardcoded utc and found the following commit 839eb52.
The mentioned issue in the time crate time-rs/time#380, has been closed and to check if the
now_local()function now works on unix-based systems, I've forked the crate, removed the "unix utc hardcode" part: VeldoraTheDragon@888ab04 and used it in my program, which then worked flawlessly.Is there a possibility to remove it aswell, so unix-based systems can again use local-time?
The current solutions seems more like a workaround to me than a proper solution.
Thanks.