zdenek.wagner at gmail.com
Thu Nov 1 16:45:50 CET 2012
2012/11/1 Herbert Voss <Herbert.Voss at fu-berlin.de>:
> Am 01.11.2012 15:14, schrieb Norbert Preining:
>>>> isn't it just because the time changes since daylight savings ended?
>>> hm, I suppose more an automatic time correction by my Linux
>>> system. I was only wondering why tlmgr should depend on it.
>> Indeed. I assume now that the time call used by perl links to the
>> syscall and that is depending on the current summer/normal time
>> So if you update exactely during the change (Herbert, when was that,
>> I cannot see it from your log!), then this is to be expected.
> I got it: my system clock is synchronized with the net time
> and I do not know why it was not done immediately after booting.
> So it happend when tlmgr was running. Nice feature ... :-)
This is caused by the changed way of handling time sync in nowaday's
Linux distros using chrony. They no longer set the HW clock if it is
more than 15 minutes off which is quite common after you take a new
computer off the box. This is the response I got after my bug report:
I'm not sure where it came from, but your RTC is off by one hour. As
hwclock --systohc is no longer called on shutdown/reboot, it needs to
be run manually when it's off by more than 15 minutes, because the
kernel RTC sync doesn't know/care about timezones and will adjust the
clock only within +/- 15 minutes.
It is sufficient to do it just once. If you do not do it, you will
have incorrect time after each reboot and the delay depends on
availability of the NTP servers.
You can look at:
Originally I did not know where the problem comes from so the
discussion is lengthy byt the last answer by M. Lichvar is exactly
what I needed and it solved the problems.
More information about the tex-live