diff options
| author | David Oberhollenzer <david.oberhollenzer@tele2.at> | 2018-07-22 20:55:34 +0200 |
|---|---|---|
| committer | David Oberhollenzer <david.oberhollenzer@tele2.at> | 2018-07-22 21:38:14 +0200 |
| commit | c3249ae0c9777e8d16c90ce1ca441e90ad4fcf7b (patch) | |
| tree | 314681ced1099af8e0b6c1c85e33a56eb5efeb51 /services/swclock.in | |
| parent | 056d3c8e6481088b8e5d9791d8c1762a3c8d1a83 (diff) | |
Add swclock service for systems without a hardware RTC
Some systems don't have a hardware real time clock and don't know the time
after bootin. An obvious soulution for this is to use time from an ntp
server. Unfortunately that requires domain name resolution, which resolvers
like unbound won't do for us, if the DNSSEC certificates aren't valid, which
they aren't if we start out with a time around 1970-1-1.
The "software clock" service tries to provide a workaround by restoring a
reasonably valid time from a backup file during boot, which we update when
shuting down. If we wan't a more correct time, we have to update it from
NTP in between.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
Diffstat (limited to 'services/swclock.in')
| -rw-r--r-- | services/swclock.in | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/services/swclock.in b/services/swclock.in new file mode 100644 index 0000000..02c4c27 --- /dev/null +++ b/services/swclock.in @@ -0,0 +1,6 @@ +description restore saved time from last shutdown +type wait +target boot +before sysinit +after vfs modules +exec xargs -a @STATEFILESPATH@/swclock date --utc |