diff options
author | Kay Sievers <kay@vrfy.org> | 2014-07-27 00:11:08 +0200 |
---|---|---|
committer | Kay Sievers <kay@vrfy.org> | 2014-07-27 10:44:31 +0200 |
commit | c264aeab4b0e7b69f469e12e78d4a48b3ed7a66e (patch) | |
tree | a99191d8ebde57537e362f6053074609bf19d7cc /src/timesync/timesyncd.h | |
parent | c6a373a26348544d944b08bf0c5dea4f72f6980b (diff) |
core: only set the kernel's timezone when the RTC runs in local time
We can not reliably manage any notion of local time. Every daylight
saving time change or time zone change by traveling will make the
time jump, and the local time might jump backwards which creates
unsolvable problems with file timestamps.
We will no longer tell the kernel our local time zone and leave
everything set to UTC. This will effectively turn FAT timestamps
into UTC timestamps.
If and only if the machine is configured to read the RTC in local
time mode, the kernel's time zone will be configured, but
systemd-timesysnc will disable the kernel's system time to RTC
syncing. In this mode, the RTC will not be managed, and external
tools like Windows bootups are expected to manage the RTC's time.
https://bugs.freedesktop.org/show_bug.cgi?id=81538
Diffstat (limited to 'src/timesync/timesyncd.h')
-rw-r--r-- | src/timesync/timesyncd.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/timesync/timesyncd.h b/src/timesync/timesyncd.h index 52cca6d1ed..e723404d82 100644 --- a/src/timesync/timesyncd.h +++ b/src/timesync/timesyncd.h @@ -97,6 +97,9 @@ struct Manager { /* Retry connections */ sd_event_source *event_retry; + + /* RTC runs in local time, leave it alone */ + bool rtc_local_time; }; const struct ConfigPerfItem* timesyncd_gperf_lookup(const char *key, unsigned length); |