> do no actual drift correction at boot, as the kernel does that by itself
I found that the only place which potentially would do that is /etc/init.d/hwclock.sh, but this would only be run under SysV init which we never supported and don't even have binary packages for. Under upstart, /etc/init/hwclock.conf uses --noadjfile and parses the UTC setting from /etc/default/rcS (that needs to be fixed), under systemd the file is masked and systemd itself parses the third line to determine UTC vs. LOCAL. I'm currently running an archive grep for "default/rcS|adjtime" to find and review all users of either. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1541532 Title: migrate UTC setting from /etc/default/rcS to adjtime Status in systemd package in Ubuntu: Triaged Bug description: This has been an Ubuntu delta in systemd and perhaps other Ubuntu packages for a long time. But /etc/default/rcS is a SysV-ism, and no other setting in there is relevant. Steps: * Bump the version guard in systemd.conf for migrating the actual setting (keep until 16.04 LTS) * Ensure that we only look at the LOCAL setting during boot, and do no actual drift correction at boot, as the kernel does that by itself. * grep the archive for software which might directly look at or even write that file (Ubuntu specific config tools and the like). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1541532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
