On Fri, Sep 18, 2015 at 3:55 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote:
> On Fri, Sep 18, 2015 at 10:44 AM, lucien xin <lucien@gmail.com> wrote:
>> I have some services which need to start after "network.target", and
>> shutdown before "netwo
>
> yes
>
> while it make sno difference if you define Before= in one unit or After= in
> the other, if a service at shutdown should be stopped before another one it
> needs just to be startet afterward at boot
>
> and it makes sense
>
> * something needs networking
> * so it is started after
On Fri, Sep 18, 2015 at 5:11 PM, Reindl Harald <h.rei...@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 m
I have some services which need to start after "network.target", and
shutdown before "network.target". but systemd didn't know "teamd" also
belongs to "network.target", so it won't shutdown the service before
"teamd".
to workaround it, I need to define "After=teamd@team0.service
On Fri, Sep 18, 2015 at 4:44 PM, Reindl Harald <h.rei...@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=net
