2 Commits

Author	SHA1	Message	Date
Zbigniew Jędrzejewski-Szmek	3b02170360	unit: do not order timers.target before basic.target ... Since commit 19f8d03783 'timer: order OnCalendar units after timer-sync.target if DefaultDependencies=no' timers might get a dependency on time-sync.target, which does not really belong in early boot. If ntp is enabled, time-sync.target might be delayed until a network connection is established. It turns out that majority of timer units found in the wild do not need to be started in early boot. Out of the timer units available in Fedora 21, only systemd-readahead-done.timer and mdadm-last-resort@.timer should be started early, but they both have DefaultDependencies=no, so are not part of timers.target anyway. All the rest look like they will be fine with being started a bit later (and the majority even much later, since they run daily or weekly). Let timers.target be pulled in by basic.target, but without the temporal dependency. This means timer units are started on a "best effort" schedule. https://bugzilla.redhat.com/show_bug.cgi?id=1158206	2014-11-02 12:33:54 -05:00
Lennart Poettering	e3d84721dc	units: introduce new timers.target and paths.target to hook timer/path units into for boot	2013-03-25 21:28:30 +01:00