[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#751238: Reopen bug report for switching hwclock-set to use hctosys



Am 09.10.2014 um 00:54 schrieb Ben Hutchings:
> On Thu, 2014-10-09 at 00:14 +0200, Michael Biebl wrote:
>> Am 08.10.2014 um 23:20 schrieb Ben Hutchings:
>>> With those exact same versions, I still see the system clock set
>>> correctly!
>>
>> What's your timezone? Mine is Europe/Berlin.
> 
> Europe/London, which is currently at +0100.
> 
>> On each reboot, my hwclock will be off by another -2 hours.
>> So if it's 12:00 local time, after reboot, my hwclock will be set to
>> 10:00, after another reboot it is set to 08:00 and so on (checked with
>> hwclock --debug).
> 
> Is the system clock consistent with the RTC after each boot?  If so, the
> RTC is being set during shutdown as if it's UTC, not local time.  If
> not, then there is a double adjustment during boot.
> 

I don't think the hwclock is set on shutdown at all under systemd.
Under sysvinit there is /etc/init.d/hwclock.sh which runs hwclock
--systohc. Afaics that's the reason why --hctosys during boot doesn't
have any ill effects under sysvinit.





-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: