[arch-general] systemd timers: switch default target to timers.target?

Thomas Bächler thomas at archlinux.org
Wed Oct 8 20:59:21 UTC 2014

Am 08.10.2014 um 20:28 schrieb Damien Robert:
> Thomas Bächler  wrote in message <543579D1.4010902 at archlinux.org>:
>> I don't care what upstream recommends, there is no reason for this
>> target to exist and there is no reason to use it. Things get even worse,
>> since you cannot order the unit After=something - since timers.target
>> pulls the unit, it gets an implicit ordering Before=timers.target,
>> removing lots of flexibility with regards to ordering (since
>> timers.target is before sysinit.target).
> I don't really care about timers.target, but shouldn't the dependency be
> put in the corresponding services files rather than in the timers? I
> personally see timers as similar to sockets files, essentially trivial to
> launch, all the work being done in the services files.

The point with sockets and paths has been made clear in the original
systemd blog post:

You first set up all socket and path units, then you can start all
daemons in parallel without caring for ordering. That is why there is a
strict ordering between sockets/paths and normal services.

Timers fulfill no such requirement. They are supposed to be started
whenever the init system can do it.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20141008/85c5240c/attachment.bin>

More information about the arch-general mailing list