[tz] Tzdata - timedatectl issue
Prasanth Ramesh
ragaprasanth at gmail.com
Wed Jun 23 10:59:03 UTC 2021
Found ZIC_BLOAT_DEFAULT change from fat to slim caused this,
fixed it by adding the ZFLAGS to fat.
Thanks & Regards,
Prasanth
On Fri, Jun 18, 2021 at 2:04 PM Prasanth Ramesh <ragaprasanth at gmail.com>
wrote:
> Hi,
>
> I am facing an issue with the timedatectl command outputs which were
> wrong from 2020b version tzdata (Local time & Time zone) values were wrong
> are there any changes happened relevant to this?
>
> *From- tzdata-2020b version - Broken*
> #timedatectl
>
> * Local time: Fri 2019-11-29 16:42:57 * Universal time:
> Fri 2019-11-29 16:42:57 UTC
> RTC time: n/a
>
> * Time zone: Asia/Kolkata (, +0000)* System clock
> synchronized: no
> NTP service: inactive
> RTC in local TZ: no
>
>
> *Before tzdata-2020a - Good*#timedatectl
>
> * Local time: Fri 2019-11-29 22:03:40 IST* Universal
> time: Fri 2019-11-29 16:33:40 UTC
> RTC time: n/a
>
> * Time zone: Asia/Kolkata (IST, +0530)* System clock
> synchronized: no
> NTP service: inactive
> RTC in local TZ: no
>
>
> Thanks & Regards,
> Prasanth
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tz/attachments/20210623/8467af88/attachment.htm>
More information about the tz
mailing list