[systemd-devel] Have timers fire after boot is complete

Frederic Crozat fcrozat at suse.com
Thu Sep 27 06:08:47 PDT 2012

Le jeudi 27 septembre 2012 à 12:55 +0000, "Jóhann B. Guðmundsson" a
écrit :
> On 09/27/2012 11:17 AM, Frederic Crozat wrote:
> > Le jeudi 27 septembre 2012 à 11:07 +0000, "Jóhann B. Guðmundsson" a
> > écrit :
> >> On 09/27/2012 08:33 AM, Christian Seiler wrote:
> >>> one of the most-requested features that is not present in systemd
> >>> currently is a true rc.local-type functionality that runs after all
> >>> other services.
> >> Any particular reason why those user just dont create type oneshot unit
> >> then order it as they see fit with after and or before?
> > Mostly because many users have no idea after which units they should
> > schedule their target. And they are used to having a "run as last"
> > script in their distribution
> Ordering it after the default target should suffice.

I tested that a loong time ago and it wasn't working as expected (but I
should re-test that).

> In Fedora we still support rc.local we just dont ship it by default so 
> if you want/prefer the old behavior.

We also have boot.local (which is equivalent to rc.local) and correctly
handled by systemd.

> >   (see
> > https://bugzilla.novell.com/show_bug.cgi?id=778715 which links to
> > openSUSE forum on this topic).
> >
> Out of the four forum samples in comment 2 on this bug, 3 of the forum 
> post ( from the look of it ) are workarounds for genuine bugs and one 
> should belong in a rule-*/route-* files under /etc/sysconfig/network 
> which would be picked up by networking scripts ( given that suse 
> networking scripts support that ) .

I didn't had time to reply to this bug, yet. I think we (systemd
community) need to improve documentation for people who need to write
workarounds (or whatever we call them) and were used to after.local (or
whatever it is called in various distributions).

Frederic Crozat <fcrozat at suse.com>

More information about the systemd-devel mailing list