From: Philip Withnall Date: Thu, 20 Apr 2017 10:34:26 +0000 (+0100) Subject: man: Fix reference to timer-sync.target instead of time-sync.target (#5764) X-Git-Tag: v234~316 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=46ae28d8c3b3c438dd1796b78bbff8f9dc188b31;p=thirdparty%2Fsystemd.git man: Fix reference to timer-sync.target instead of time-sync.target (#5764) Also fix an erroneous reference to it in the NEWS file, for posterity. Signed-off-by: Philip Withnall --- diff --git a/NEWS b/NEWS index f177ca31e64..73ee35f53c8 100644 --- a/NEWS +++ b/NEWS @@ -3318,7 +3318,7 @@ CHANGES WITH 216: like Cockpit which register web clients as PAM sessions. * timer units with at least one OnCalendar= setting will now - be started only after timer-sync.target has been + be started only after time-sync.target has been reached. This way they will not elapse before the system clock has been corrected by a local NTP client or similar. This is particular useful on RTC-less embedded diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 4fe140e4bc3..7102d626e1b 100644 --- a/man/systemd.timer.xml +++ b/man/systemd.timer.xml @@ -93,7 +93,7 @@ on timers.target, as well as Conflicts= and Before= on shutdown.target to ensure that they are stopped cleanly prior to system shutdown. Timer units with at least one OnCalendar= directive will have an additional After= - dependency on timer-sync.target to avoid being started before the system clock has been + dependency on time-sync.target to avoid being started before the system clock has been correctly set. Only timer units involved with early boot or late system shutdown should disable the DefaultDependencies= option.