You are not logged in.
Daylight savings time today and my Gnome 3 install is set to automatically update the date and time. It's still showing me an hour behind. I looked at the wiki and confirmed that the ntpd.service is running. (I used both systemctl start and ntpd -u ntp:ntp). I temporarily stopped it and ran sudo ntpd -qq as suggested by the wiki. The output is
10 Mar 10:04:54 ntpd[13651]: ntpd 4.2.8p12@1.3728-o Wed Sep 26 18:50:12 UTC 2018 (1): Starting
10 Mar 10:04:54 ntpd[13651]: Command line: ntpd -qg
10 Mar 10:04:54 ntpd[13651]: proto: precision = 0.060 usec (-24)
10 Mar 10:04:54 ntpd[13651]: Listen and drop on 0 v6wildcard [::]:123
10 Mar 10:04:54 ntpd[13651]: Listen and drop on 1 v4wildcard 0.0.0.0:123
10 Mar 10:04:54 ntpd[13651]: Listen normally on 2 lo 127.0.0.1:123
10 Mar 10:04:54 ntpd[13651]: Listen normally on 3 wlo1 192.168.86.59:123
10 Mar 10:04:54 ntpd[13651]: Listen normally on 4 lo [::1]:123
10 Mar 10:04:54 ntpd[13651]: Listen normally on 5 wlo1 [fe80::ff80:6273:317b:dfd8%2]:123
10 Mar 10:04:54 ntpd[13651]: Listening on routing socket on fd #22 for interface updates
10 Mar 10:05:02 ntpd[13651]: ntpd: time slew -0.000337 s
ntpd: time slew -0.000337sAfter that, executing date still shows the time an hour behind. Any idea where I've gone wrong? Looking at the timezone status it shows ntpd as inactive even though it's running:
timedatectl status
Local time: Sun 2019-03-10 10:10:23 EST
Universal time: Sun 2019-03-10 15:10:23 UTC
RTC time: Sun 2019-03-10 15:10:23
Time zone: EST (EST, -0500)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: noLast edited by viniosity (2019-03-11 01:04:58)
Offline
ntpd will only update a certain amount by default. If that output is current, your time is over 5 hours off. Set it closer.
Edit: looking again, I bet the problem is not understanding the difference between UTC and localtime, and how your RTC is set. The time page in the wiki covers all of this pretty well.
Last edited by Scimmia (2019-03-10 20:26:43)
Offline
I was wondering if it was because the timezone was set to EST. EST is a fixed offset from UTC. Locations using DST would switch to EDT.
Last edited by loqs (2019-03-10 20:38:31)
Offline
Since there's no zoninfo for EDT, move to "US/Eastern"
Offline
Since there's no zoninfo for EDT, move to "US/Eastern"
Setting my timezone to New York fixed it, thank you all!
timedatectl set-timezone America/New_YorkOffline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Offline
And yet your Universal Time is wrong, unless the info in your first post was old when you posted it.
Offline
And yet your Universal Time is wrong, unless the info in your first post was old when you posted it.
It was. I wrote it, did more research, read the wiki again, and then posted.
Offline
For over 5 hours?
Offline