Re: systemd, ntp, kernel and hwclock
- To: firstname.lastname@example.org
- Subject: Re: systemd, ntp, kernel and hwclock
- From: Roger Lynn <Roger@rilynn.me.uk>
- Date: Sat, 4 Mar 2017 20:33:09 +0000
- Message-id: <[🔎] email@example.com>
- In-reply-to: <tfEiZfirstname.lastname@example.org>
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
On 28/02/17 01:00, Ben Hutchings wrote:
> On Mon, 2017-02-27 at 16:09 -0800, Russ Allbery wrote:
>> Right, ntpdate for some reason doesn't set the flag to do this.
> There is a very good reason, which is that without continuous
> adjustment the system clock cannot be assumed more stable than the RTC.
This doesn't make sense to me. Most users are probably not aware that there
is a separate hardware RTC. Why would one assume that the clock the user is
not aware of is better than the clock the user can see and is presumably