Le lundi 05 décembre 2011 à 04:49 -0500, Mark Gray a écrit :
On Mon, Dec 5, 2011 at 4:14 AM, Frederic Crozat <fcrozat@suse.com> wrote: [snip]
boot.local is still supported by way of rc-local.service: [snip]
yep.. Beware it might not be started as the really "last" service gefore getty..
I worry about that, because I always used to use after.local in order to be sure that everything my local services needed was already up and running. It is easy enough to add after.local myself, but since it is no longer expected by systemd doing so would make me nervous, so I just put all my after.local scripting into boot.local and crossed my fingers. So far it seems to work, but I would be a happier camper if the concept of an after.local was still implemented by systemd.
Unfortunately, since there is no "static list" of services, unlike sysvinit (which is why insserv was able to ensure non-LSB standard $ALL target), I don't expect it to happen. If you want to play it safe, you could either write your own systemd service file and add "After= ..." with the service you want to be started before your own service. Or you can use timer feature from systemd, to start a service xx seconds after the systemd is "active" (ie boot is complete), see /lib/systemd/system/systemd-readahead-done.timer (and systemd-readahead-done.service as an example). -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org