Re: systemd, ntp, kernel and hwclock
Kurt Roeckx <kurt@roeckx.be> writes:
> Having ntpdate clear the unsynced flag doesn't make sense since it would
> start writing a time to the RTC each 11 minutes, and as Ben said you
> have no idea which of the 2 clocks is the most correct one.
Oh, I thought it was a one-shot thing, but it turns on syncing behavior
from that point forward. Thanks, that was the piece that I was missing.
> I can also understand that systemd doesn't set the clock for just the
> same reason. Either the clock is synched and it's written, or it's not
> suched, it's unknown which one is the most correct, and it's not
> written.
Yeah, it now makes perfect sense to me.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to:
- References:
- systemd, ntp, kernel and hwclock
- From: Daniel Pocock <daniel@pocock.pro>
- Re: systemd, ntp, kernel and hwclock
- From: Russ Allbery <rra@debian.org>
- Re: systemd, ntp, kernel and hwclock
- From: Daniel Pocock <daniel@pocock.pro>
- Re: systemd, ntp, kernel and hwclock
- From: Russ Allbery <rra@debian.org>
- Re: systemd, ntp, kernel and hwclock
- From: Ben Hutchings <ben@decadent.org.uk>
- Re: systemd, ntp, kernel and hwclock
- From: Russ Allbery <rra@debian.org>
- Re: systemd, ntp, kernel and hwclock
- From: Ben Hutchings <ben@decadent.org.uk>
- Re: systemd, ntp, kernel and hwclock
- From: Kurt Roeckx <kurt@roeckx.be>