On Tue, 2014-10-07 at 21:11 +0200, Michael Biebl wrote: > Hi Ben > > Am 07.10.2014 um 21:00 schrieb Ben Hutchings: > > On Tue, 2014-10-07 at 20:21 +0200, Michael Biebl wrote: > >> Fwiw, it was me, how experiences this issue. > >> After the switch from systz to hctosys in /lib/udev/hwclock-set, my > >> hardware clock is no longer properly set under systemd. > > > > It works for me. Which version of systemd are you using? > > $ apt-cache policy systemd util-linux initramfs-tools > systemd: > Installiert: 215-5+b1 > Installationskandidat: 215-5+b1 > Versionstabelle: > *** 215-5+b1 0 > 500 http://ftp.de.debian.org/debian/ sid/main amd64 Packages > 100 /var/lib/dpkg/status > util-linux: > Installiert: 2.25.1-3 > Installationskandidat: 2.25.1-3 > Versionstabelle: > *** 2.25.1-3 0 > 500 http://ftp.de.debian.org/debian/ sid/main amd64 Packages > 100 /var/lib/dpkg/status > initramfs-tools: > Installiert: 0.118 > Installationskandidat: 0.118 > Versionstabelle: > *** 0.118 0 > 500 http://ftp.de.debian.org/debian/ sid/main amd64 Packages > 100 /var/lib/dpkg/status With those exact same versions, I still see the system clock set correctly! > > > >> Afaics, this is because systemd set's the clock internally and doesn't > >> care for the flag file that is created by hwclock-set. > > > > Also hwclock-set explicitly checks for running under systemd and then > > does nothing. > > Right, but if hwclock-set is run in the initramfs, there is no > /run/systemd/system yet, so hwclock-set will be run, irregardless if > sysvinit or systemd will be PID 1 later on. I understand that. Ben. -- Ben Hutchings Humour is the best antidote to reality.
Attachment:
signature.asc
Description: This is a digitally signed message part