[systemd-devel] Boot ordering
Christoph.Pleger at cs.tu-dortmund.de
Thu Mar 19 05:09:42 PDT 2015
>> 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
>> multi-user.target can already be started when some jobs from
>> have not been started???
> What is the the
> problem you are trying to solve by "implementing a new 'intermediate'
> runlevel" ?
I want a program to be run at boot time without any other systemd services
starting concurrently. The program needs the services from basic.target
and may influence everything in multi-user.target and later targets, so I
guess that between basic.target and multi-user.target is a good time for
execution of the program.
I hoped that this can be achieved by simply defining a new target, setting
after basic.target dependencies for it and changing the dependencies of
multi-user.target from basic.target to my new target. This would not
require me too know anything about the specific services in basic.target
and multi-user.target .
More information about the systemd-devel