systemd - standard place to run stuff after the network is up?
awilliam at redhat.com
Mon Oct 17 19:02:20 UTC 2011
On Mon, 2011-10-17 at 09:20 -0500, Bruno Wolff III wrote:
> I want to try to modprobe netconsole during boot, but it needs to happen
> after the network is up. Is there any standard place (rc.local and
> modules-load seem to happen too early) to do this?
> I filed https://bugzilla.redhat.com/show_bug.cgi?id=746481 against systemd,
> but it has been closed notabug. So I am looking for simple alternatives
> to do this. If there aren't any, then it looks like I need to make a custom
> service that waits for networking to be up.
rc.local was intended to run after all other services on boot - it's
always S99 on 'traditional' init systems - so theoretically systemd
'ought' to have it ordered to start only after every other service's
startup is complete; it would be possible for systemd to do this, I
think, though lennart may be able to think of some reasons it might be
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
More information about the devel