Hide Forgot
Now I am in summer time I have noticed F15 gains an hour each time I reboot it. I am guessing there is something unbalanced in the start up and shut down scripts provided by systemd. Currently (as I haven't corrected the time) hwclock --show is one hour ahead of real time, the time on hte desktop is two hours ahead, /etc/sysconfig/clock contains ZONE="Europe/London" and /etc/adjtime contains 3530.393003 1301512717 0.000000 1301512717 LOCAL
Hmm, LOCAL and not UTC? /etc/sysconf/clock is mostly irrelevant, /etc/localtime matters. What does "systemctl status hwclock-load.service" say? What does "systemctl is-enabled hwclock-load.service ; echo $?" say?
# systemctl status hwclock-load.service hwclock-load.service - Apply System Clock UTC Offset Loaded: loaded (/lib/systemd/system/hwclock-load.service) Active: inactive (dead) CGroup: name=systemd:/system/hwclock-load.service # systemctl is-enabled hwclock-load.service ; echo $? 1
Ah, so it isn't enabled. "systemctl enable hwclock-load.service" should fix your problem. But I do wonder how it happened that this service isn't enabled, after all we enable it by default in %post. Is this an upgrade from an older F15/Rawhide?
It was an update from F14. The install had also gone through the F14 alpha/beta stages, so systemd-units was probably first installed when systemd was the default in F14 testing. I have checked the other services mentioned in the systemd-units scripts and getty@.service and remote-fs.target aren't enabled either.
Ah, OK, if it is such an old setup, then let's just hope this problem was due to that, and that the bug doesn't exist for fresh installs, and upgrades from a F14 final version. Closing.