On 06/10/2014 23:45, Thomas Bächler wrote:
> Am 04.10.2014 um 13:44 schrieb Neitsab:
> Why?
>
> Most of these timers should only be available when running a fully
> booted system. timers.target is pulled in by basic.target. This implies
> that startup of all normal services is delayed until the startup of
> these timers (and other units) has finished. This may make sense for
> socket or path units, but is entirely unnecessary for timer units,
> especially those that merely serve as cron replacements.
>
Upstream recommends to stick to timers.target. If units should be
delayed after others After= and Before= directives do the job. There is
also OnBootSec= if you want to delay timers on a timed way.
from (7) systemd.special:
timers.target
A special target unit that sets up all timer units (see
systemd.timer(5) for details) that shall be
active after boot.
It is recommended that timer units installed by applications
get pulled in via Wants= dependencies from
this unit. This is best configured via WantedBy=timers.target
in the timer unit's "[Install]" section.
Cheers,
--
Sébastien "Seblu" Luttringer
https://seblu.net | Twitter: @seblu42
GPG: 0x2072D77A
Attachment:
signature.asc
Description: OpenPGP digital signature
