[systemd-devel] a problem about the order of service shudown in systeamd

[lucien xin]

On Fri, Sep 18, 2015 at 4:44 PM, Reindl Harald <h.reindl at thelounge.net> wrote:
>
>
> Am 18.09.2015 um 10:34 schrieb lucien xin:
>>>
>>> Just order teamd before network.target
>>
>>
>> sorry, I cannot follow you.
>
>
> After=network.target
>
>> I mean, now my A.service is shutdown before network.target.
>> but I also wnat A.service to be shutdown before teamd,
>> define "After=teamd at team0.service teamd at team1.service...."
>> in A.service can work, but I hope there is another way,
>>
>> like there may be another option can make A.service's shutdown
>> 'level' earlier than both teamd and network.target's shutdown 'level'
>>
>> i do not know, just ask
>
>
> services are stopped in the reverse order they are started and so with
> After= and Before= you just need to adjust the order you want
>
>
okay, I got you, thanks.

is there a options that can define some common shutdown/boot order
priority? not through dependence( After= and Before= you mentioned).

for example, A.service maybe 5, network.target and teamd are 1, the
service whose order priority is 4 will be shudown earlier than that
priority is 1.
something like that. I do not know if the dependence is the only way
to define the shudown/boot order.