Bug#755722: systemd must sync systemclock to RTC on shutdown

Martin Pitt mpitt at debian.org
Fri Feb 13 06:54:11 GMT 2015

Control: reassign -1 util-linux 2.25.2-5
Control: severity -1 normal

I still disagree with critical:

 - If the hardware clock is so broken that at the next boot it has an
   earlier time than on the previous boot/ntpdate, then writing it
   once more at shutdown isn't going to entirely fix this problem, as
   it will again go sufficiently wrong if you don't reboot immediately
   but after some time.

 - Second, this doesn't "break" fsck: fsck already correctly notices
   that the last write time is in the future and handles that
   appropriately; at least that's what the original reporter

Also, under sysvinit and upstart it is util-linux which does the
hwclock <-> sysclock dance, thus reassigning this. We shouldn't
put this logic into different packages for different init systems.

I also disagree this should be done in the first place. But I don't
want to put myself into eternal wars and "who shouds the loudest
wins", so I'll keep this bug open and won't make any further
Severity: adjustments.


Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150213/a9f5e848/attachment-0002.sig>

More information about the Pkg-systemd-maintainers mailing list