On May 16, 2015, at 6:02 AM, Ben Hutchings <b...@decadent.org.uk> wrote:
> This is not implemented directly by the init system. util-linux > installs the script/lib/udev/hwclock-set and a udev rule that runs it > for each RTC device. However, the hwclock-set script does nothing if > systemd is running. curiouser and curiouser… Looking at the code in /lib/udev/hwclock-set, I can’t see that it would would ever do anything useful (except by chance) in the case like mine where there are two rtc devices, only one of which should actually be used to set system time at boot. In particular, it goes to some effort to source /etc/default/rcS and /etc/default/hwclock, but it pays no attention to the HCTOSYS_DEVICE parameter. It appears to set the system time from each RTC device in turn as it discovers them. So system time ends up set by the last RTC to be discovered. If the right one happens to be last, that’s good. But that’s not guaranteed. Enjoy! Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
