Discussion:
[fedora-arm] timedatectl issue ? Love for timedatectl and nmcli !!!!!
linux guy
2017-01-31 20:06:09 UTC
Permalink
# timedatectl
Local time: Tue 2017-01-31 12:49:07 MST
Universal time: Tue 2017-01-31 19:49:07 UTC
RTC time: n/a
Time zone: America/Edmonton (MST, -0700)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: yes

Warning: The system is configured to read the RTC time in the local time
zone.
This mode can not be fully supported. It will create various
problems
with time zone changes and daylight saving time adjustments. The
RTC
time is never updated, it relies on external facilities to
maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.

# timedatectl set-local-rtc 0
Failed to set local RTC: hwclock failed: Child process exited with code 70

BTW, I *LOVE* how timedatectl and nmcli work ! No more hunting around for
obscure commands to set things up from the command line. I couldn't
believe how easy it was to set up wifi from ssh with nmcli ! Love it !
Keep up the good work.

LG.
linux guy
2017-01-31 20:14:57 UTC
Permalink
And the documentation is very good too. That definitely helps.

https://docs.fedoraproject.org/en-US/Fedora/25/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html

https://docs.fedoraproject.org/en-US/Fedora/25/html/Networking_Guide/sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html

I'd rather have these tools than something like raspi-config
​
Daniel Laczi
2017-01-31 20:20:12 UTC
Permalink
Post by linux guy
# timedatectl
Local time: Tue 2017-01-31 12:49:07 MST
Universal time: Tue 2017-01-31 19:49:07 UTC
RTC time: n/a
Time zone: America/Edmonton (MST, -0700)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time
zone.
This mode can not be fully supported. It will create various
problems
with time zone changes and daylight saving time adjustments. The
RTC
time is never updated, it relies on external facilities to
maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.
# timedatectl set-local-rtc 0
Failed to set local RTC: hwclock failed: Child process exited with code 70
The Raspberry doesn't have a built-in RTC, so that's ok.

Daniel
Post by linux guy
BTW, I *LOVE* how timedatectl and nmcli work ! No more hunting around for
obscure commands to set things up from the command line. I couldn't
believe how easy it was to set up wifi from ssh with nmcli ! Love it !
Keep up the good work.
LG.
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm
linux guy
2017-01-31 20:29:01 UTC
Permalink
Then why do I get the warning ? Why does it say RTC in local TZ ?
​
Daniel Laczi
2017-01-31 20:35:39 UTC
Permalink
A RTC is a hardware clock. "RTC in local TZ: yes" only indicates, that
the RTC would have been in local TZ. The alternative is UTC. Please
check the warning for more information.

If you want a bit of time improvement without buying a RTC (and
configuring it...), you can use systemd-timesyncd. It basically writes
the current time periodically to a file. It also writes the time very
late on shutdown to that file and gets the time from that file at
startup early.

Cheers, Daniel
Post by linux guy
Then why do I get the warning ? Why does it say RTC in local TZ ?

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lis

Loading...