systemd: Add "After" dependency on time-sync.target #12248
Merged
+4
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Short description
Adds 'After=time-sync.target' to the service unit files; this will not have any immediate effect, unless the system administrator has also enabled a unit which has a 'Before' dependency on that target; there are none of those units enabled in a default configuration in common distributions. systemd itself adds such an 'After' dependency to all timer units with OnCalendar settings, and to some other units.
However, in a system which makes use of systemd-timesyncd, the admin can enable systemd-time-wait-sync.service, which has such a dependency. The result would be that none of the PowerDNS services on the system would be started until after systemd-timesyncd is certain that the system's clock is synchronized with the configured external source.
A similar configuration can be achieved on systems which use ntpd, chronyd, or other time synchronization tools.
Closes #11153.
Checklist
I have: