$ timedatectl
Local time: Fri 2015-01-30 11:04:51 CET correct UTC+1
Universal time: Fri 2015-01-30 10:04:51 UTC correct UTC
Timezone: Europe/Budapest (CET, +0100) correct
NTP enabled: n/a
NTP synchronized: no
RTC in local TZ: no ? UTC then ?
DST active: no
Last DST change: DST ended at
Sun 2014-10-26 02:59:59 CEST
Sun 2014-10-26 02:00:00 CET
Next DST change: DST begins (the clock jumps one hour forward) at
Sun 2015-03-29 01:59:59 CET
Sun 2015-03-29 03:00:00 CEST
$ sudo hwclock
Fri Jan 30 12:05:09 2015 -0.406771 seconds ??????? UTC+2 ??????
$ date
Fri Jan 30 11:08:30 CET 2015 correct
The documentation of hwclock says that it always displays local time, no matter whether RTC is set according to local or universal time.
What could cause hwclock to display UTC+2 as the local time?
I originally thought that hwclock "believes" the RTC to be set according to UTC, hence it displays +1, since I am in central Europe, but the RTC is actually in local time (+1 already) hence it disaplays +1+1=+2. But timedatectl above "says" that RTC is not local. So what is going on?
update:
$ sudo hwclock --debug
hwclock from util-linux 2.20.1
Using /dev interface to clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2015/01/30 11:38:38
Hw clock time : 2015/01/30 11:38:38 = 1422617918 seconds since 1969
Fri Jan 30 12:38:38 2015 -0.516275 seconds
So it "thinks" RTC is UTC but is actually local. Hence timedatectl is the culprit?
