On Mon, Dec 04, 2023 at 06:29:24AM -0500, gene heskett wrote: > On 12/4/23 05:03, Anssi Saari wrote: > > timedatectl timesync-status > root@mkspi:/etc# timedatectl timesync-status > Failed to query server: Connection timed out > > This printer is running chrony, which removes timesyncd. > > ntpsec on this machine is working, even the seconds match and the log shows > the request being serviced: > > 06:19:05.847872 eno1 In IP mkspi.coyote.den.48265 > coyote.coyote.den.ntp: > NTPv4, Client, length 48 > 06:19:05.848004 eno1 Out IP coyote.coyote.den.ntp > mkspi.coyote.den.48265: > NTPv4, Server, length 48 > > but the printer is on PST where I'm on EST, 4 hours difference and the > printer is ignoring /etc/timezone. Why? What can override it? Please, don't mix up local time (a device to show to you, done somewhere in libc) with kernel time (as traded between NTP and friends). That way lies madness. Kernel time is *always* number of seconds since some Epoch (typically 1970-01-01). No EST or whatever nonsense in there. And this is the terms in which NTPs trade (OK, they have fractions of sec in there, but that's it). Nothing else. Unix boxes aren't DOS, haven't ever been. Actually you should know that. Cheers -- t
Attachment:
signature.asc
Description: PGP signature