Re: systemd, ntp, kernel and hwclock
- To: debian-devel@lists.debian.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: <[🔎] 5tkrod-nff.ln1@silverstone.rilynn.me.uk>
- In-reply-to: <tfEiZ-576-5@gated-at.bofh.it>
- References: <afac576b-b2f3-ab27-124f-e58e1ac14561@pocock.pro> <8737ezl9we.fsf@hope.eyrie.org> <3473139f-499e-ea04-86dc-ca687acb6331@pocock.pro> <87h93fjhvt.fsf@hope.eyrie.org> <1488242059.2821.3.camel@decadent.org.uk>
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
happy with?
Roger
Reply to: