Le mardi 06 novembre 2012 à 12:01 +0100, Dr. Werner Fink a écrit :
Hi,
due several bug reports, I'm currently reading the code of systemd-195 as found in oS:Factory. I'm a bit surprised about some missing features and bottlenecks:
* There is no --adjust functionality to handle systematic drift of the HW/RTC clock of the BIOS * There is no --badyear functionality for broken some Award BIOS * It ignores s390 as well as XEN clients * It does not provide --systohc functionality which had lead to several bug reports about the fact that the system clock is not written back to RTC at shutdown/reboot * It does not check for the SUSE /dev/shm/warpclock ... OK this does not cause a problem as settimeofday(2) with its timezone is sealed within the kernel after warpclock has been called in the initrd. I'm wondering how the timestamps of the root file system will be repaired if the timezone correction would not be done in the initrd.
... the question rises if we should try to implement this in the C source of systemd (src/shared/hwclock.c and src/timedate/timedated.c) or is there a way to avoid the systemd-timed service with a more complete but shell code script executed by a systemd service unit at boot as as at shutdown/reboot.
It would be much better to raise those points directly on upstream
mailing list, since they are not openSUSE specific (and I don't know how
they are handled by other distributions either).
--
Frederic Crozat