Bug#755722: [pkg-ntp-maintainers] Processed: Re: systemd: Warning on each reboot: Superblock last write time is in the future

[Jon Severinsson]

torsdag 24 juli 2014 00:02:09 skrev du:
> reassign -1 systemd-sysv
> thanks
> 
> I strongly disagree that ntpdate or ntp should be setting the RTC.
> ntp doesn't know anything about the RTC, nor should it know
> anything about it.  It's only concerned with the system clock.

ntp already do set the RTC (or more accurately, tells the kernel to do so), it 
is only ntpdate that doesn't.

> It seems only logical that the writing should also be done by
> init, like it always has.

sysvinit has never read from, nor written to, the RTC, and only recently did 
systemd start reading from the RTC, in order to get a reasonably accurate 
system clock before starting any services that might rely on that.

Under sysvinit  hwclock from util-linux used to read the RTC and overwrite the 
system clock partway through the boot, and then overwrite the RTC with the 
system clock partway through the shutdown.

As a result, hwclock would override the RTC on every clean shutdown, even 
though dedicated HW are often less inaccurate than the software system clock. 
Additionally there was a risk of loosing an accurate time sync in the event of 
an unclean shutdown.

Systemd upstream is generally not satisfied with this sort of half-measures, 
and aims to get rid of them as soon as a better solution is made available.  
As both the main ntp daemon and the new systemd-timesyncd daemon do write to 
the RTC whenever they acquire an accurate time, the traditional band-aid at 
shutdown where deemed unnecessary, and so they naturally removed it.

As suitable alternatives are available I do not find it warranted to override 
upstream on this.  But if you are not interest in working on fixing the issue 
from your side we can simply add a Breaks: on ntpdate in systemd instead.

Please let me know how you would like me to proceed.

Regards
Jon Severinsson