[systemd-devel] Boot ordering

Andrei Borzenkov arvidjaar at gmail.com
Thu Mar 19 03:45:53 PDT 2015

On Thu, Mar 19, 2015 at 1:00 PM, Christoph Pleger
<Christoph.Pleger at cs.tu-dortmund.de> wrote:
> Hello,
>>> I am experimenting a little with systemd and trying to define a new
>>> "intermediate" runlevel, a runlevel between basic.target and
>>> multi-user.target. This means that I want the services which are
>>> required
>>> by my new runlevel to be started after all services from basic.target
>>> have
>>> been started and to be finished before any service from
>>> multi-user.target
>>> is started.
>> There is no feasible way to do it right now.
> So, if the original unit file multi-user.target contains
> After=basic.target rescue.service rescue.target
> this "after" does not really mean anything and jobs wanted or required by
> multi-user.target can already be started when some jobs from basic.target
> have not been started???

After means exactly what it says - multi-user.target waits for all
units listed in After line. It does not imply anything about relative
ordering of those units. Unless they have other dependencies all of
them will (attempted to) be started in parallel.

More information about the systemd-devel mailing list