Am 08.10.2014 um 02:51 schrieb Sébastien Luttringer:
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
Thomas Bächler wrote in message 543579d1.4010...@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
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
On 05/10/2014 20:21, Rodrigo Rivas wrote:
On Sat, Oct 4, 2014 at 1:44 PM, Neitsab neit...@ovh.fr wrote:
$ pkgfile --glob *.timer | xargs -n1 pkgfile --list | grep .timer$
/usr/lib/systemd/system/mailman-checkdbs.timer
/usr/lib/systemd/system/mailman-cullbadshunt.timer
Am 04.10.2014 um 13:44 schrieb Neitsab:
Hi everybody,
It seems like systemd now provides a target that is intended to gather
all timers supposed to be activated after boot.
This target that systemd now provides has always been available.
Currently, three timers are statically enabled via
On Sat, Oct 4, 2014 at 1:44 PM, Neitsab neit...@ovh.fr wrote:
Five other packages in base group provide systemd timers: logrotate,
man-db, mdadm, shadow and util-linux. I didn't manage to use pkgfile to
get this list (globbing and regex switches didn't help, dunno why), so I
only counted
Hi everybody,
It seems like systemd now provides a target that is intended to gather
all timers supposed to be activated after boot. From man 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.
7 matches
Mail list logo
