Systemd/units/systemd-timesyncd.service.in

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Network Time Synchronization
Documentation=man:systemd-timesyncd.service(8)
ConditionCapability=CAP_SYS_TIME
DefaultDependencies=off
RequiresMountsFor=/var/lib/systemd/clock
After=systemd-remount-fs.service systemd-tmpfiles-setup.service systemd-sysusers.service
Before=sysinit.target shutdown.target
Conflicts=shutdown.target
Wants=time-sync.target
Before=time-sync.target

[Service]
Type=notify
Restart=always
RestartSec=0
ExecStart=@rootlibexecdir@/systemd-timesyncd
CapabilityBoundingSet=CAP_SYS_TIME CAP_SETUID CAP_SETGID CAP_SETPCAP CAP_CHOWN CAP_DAC_OVERRIDE CAP_FOWNER
PrivateTmp=yes
PrivateDevices=yes
ProtectSystem=full
ProtectHome=yes
WatchdogSec=1min

[Install]
WantedBy=sysinit.target
timesyncd: add unit and man page 2014-04-29 08:57:51 +02:00			`# This file is part of systemd.`
			`#`
			`# systemd is free software; you can redistribute it and/or modify it`
			`# under the terms of the GNU Lesser General Public License as published by`
			`# the Free Software Foundation; either version 2.1 of the License, or`
			`# (at your option) any later version.`

			`[Unit]`
			`Description=Network Time Synchronization`
			`Documentation=man:systemd-timesyncd.service(8)`
			`ConditionCapability=CAP_SYS_TIME`
timesyncd: save clock to disk everytime we get an NTP fix, and bump clock at boot using this This is useful to make sure the system clock stays monotonic even on systems that lack an RTC. Also, why we are at it, also use the systemd release time for bumping the clock, since it's a slightly less bad than starting with jan 1st, 1970. This also moves timesyncd into the early bootphase, in order to make sure this initial bump is guaranteed to have finished by the time we start real daemons which might write to the file systemd and thus shouldn't leave 1970's timestamps all over the place... 2014-05-20 17:04:11 +02:00			`DefaultDependencies=off`
			`RequiresMountsFor=/var/lib/systemd/clock`
units: rebuild /etc/passwd, the udev hwdb and the journal catalog files on boot Only when necessary of course, nicely guarded with the new ConditionNeedsUpdate= condition we added. 2014-06-13 13:10:30 +02:00			`After=systemd-remount-fs.service systemd-tmpfiles-setup.service systemd-sysusers.service`
timesyncd: save clock to disk everytime we get an NTP fix, and bump clock at boot using this This is useful to make sure the system clock stays monotonic even on systems that lack an RTC. Also, why we are at it, also use the systemd release time for bumping the clock, since it's a slightly less bad than starting with jan 1st, 1970. This also moves timesyncd into the early bootphase, in order to make sure this initial bump is guaranteed to have finished by the time we start real daemons which might write to the file systemd and thus shouldn't leave 1970's timestamps all over the place... 2014-05-20 17:04:11 +02:00			`Before=sysinit.target shutdown.target`
			`Conflicts=shutdown.target`
units: pull in time-sync.target from systemd-timedated.service After all, that's what we document for time-sync.target in systemd.special(5), hence let's follow our own suggestion. 2014-06-06 16:20:33 +02:00			`Wants=time-sync.target`
			`Before=time-sync.target`
timesyncd: add unit and man page 2014-04-29 08:57:51 +02:00
			`[Service]`
			`Type=notify`
			`Restart=always`
			`RestartSec=0`
			`ExecStart=@rootlibexecdir@/systemd-timesyncd`
timesyncd: only update stamp file when we are synchronized Create initial stamp file with compiled-in time to prevent bootups with clocks in the future from storing invalid timestamps. At shutdown, only update the timestamp if we got an authoritative time to store. 2014-05-22 14:31:46 +02:00			`CapabilityBoundingSet=CAP_SYS_TIME CAP_SETUID CAP_SETGID CAP_SETPCAP CAP_CHOWN CAP_DAC_OVERRIDE CAP_FOWNER`
timesyncd: run timesyncd as unpriviliged user "systemd-timesync" (but still with CAP_SYS_TIME) 2014-05-17 20:33:47 +02:00			`PrivateTmp=yes`
			`PrivateDevices=yes`
core: rename ReadOnlySystem= to ProtectSystem= and add a third value for also mounting /etc read-only Also, rename ProtectedHome= to ProtectHome=, to simplify things a bit. With this in place we now have two neat options ProtectSystem= and ProtectHome= for protecting the OS itself (and optionally its configuration), and for protecting the user's data. 2014-06-04 18:07:55 +02:00			`ProtectSystem=full`
			`ProtectHome=yes`
timesyncd: enable watchdog support 2014-05-17 21:11:00 +02:00			`WatchdogSec=1min`
timesyncd: add unit and man page 2014-04-29 08:57:51 +02:00
			`[Install]`
timesyncd: save clock to disk everytime we get an NTP fix, and bump clock at boot using this This is useful to make sure the system clock stays monotonic even on systems that lack an RTC. Also, why we are at it, also use the systemd release time for bumping the clock, since it's a slightly less bad than starting with jan 1st, 1970. This also moves timesyncd into the early bootphase, in order to make sure this initial bump is guaranteed to have finished by the time we start real daemons which might write to the file systemd and thus shouldn't leave 1970's timestamps all over the place... 2014-05-20 17:04:11 +02:00			`WantedBy=sysinit.target`