Bug#751238: Reopen bug report for switching hwclock-set to use hctosys
On Tue, Oct 07, 2014 at 08:40:26PM +0200, Michael Biebl wrote:
> Am 07.10.2014 um 20:37 schrieb Aurelien Jarno:
> > On Tue, Oct 07, 2014 at 08:21:51PM +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.
> >>
> >> Afaics, this is because systemd set's the clock internally and doesn't
> >> care for the flag file that is created by hwclock-set.
> >> Under sysvinit, I don't encounter this problem.
> >>
> >> When switching hwclock-set back to systz, it works properly for both
> >> systemd and sysvinit.
> >
> > I don't really see how it can happen, this file is not supposed to be
> > run under systemd, due to the following code at the beginning:
> >
> > | if [ -e /run/systemd/system ] ; then
> > | exit 0
> > | fi
> >
> > Therefore it should not be run on systemd. It was actually one of the
> > problem I reported on IRC before we switched all the RTC drivers to
> > built-in.
>
> Keep in mind, that /run/systemd/system does not exist in the initramfs
> as we don't use systemd in the initramfs (yet).
> So afaics what happens is, that we run hwclock twice under systemd:
> once in the initramfs, a second time by systemd itself.
>
Oh running hwclock from the initramfs is something new then. At the time
I reported the bug this was not the case. I still don't get why it
doesn't work though. Running hwclock --hctosys in the initramfs should
not be different than what the kernel does for built-in modules.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: