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

lucien xin lucien.xin at gmail.com
Fri Sep 18 02:51:52 PDT 2015


On Fri, Sep 18, 2015 at 5:11 PM, Reindl Harald <h.reindl at thelounge.net> wrote:
>
>
> Am 18.09.2015 um 11:03 schrieb lucien xin:
>>
>> is there a options that can define some common shutdown/boot order
>> priority? not through dependence( After= and Before= you mentioned).
>
>
> no, and it makes no sense at all
>
> wether servcies are dpending on each other then you need to define
> dependencies and if they are not they don't need to be ordered and can start
> in parallel
>
>> 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.
>
>
> that would be unmanageable because it interfers with Before/After/Requires
> and at the end of the day you have conflicts or no idea what is schedlued
> how and why
>
>
okay,

as to the case I mentioned, if A.service want to be shutdown before
teamd,
the only way is to configure After=/Before= options in A.serivce, right ?


More information about the systemd-devel mailing list