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

Am 18.09.2015 um 11:51 schrieb lucien xin: On Fri, Sep 18, 2015 at 5:11 PM, Reindl Harald 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

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

On Fri, Sep 18, 2015 at 10:44 AM, lucien xin wrote: > 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 >

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

On Fri, Sep 18, 2015 at 3:55 PM, Andrei Borzenkov wrote: > On Fri, Sep 18, 2015 at 10:44 AM, lucien xin wrote: >> I have some services which need to start after "network.target", and >> shutdown before "network.target". but systemd didn't know "teamd"

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

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@team0.service

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

On Fri, Sep 18, 2015 at 12:03 PM, lucien xin wrote: > > 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

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

> > 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

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

On Fri, Sep 18, 2015 at 5:11 PM, Reindl Harald 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

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

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

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

On Fri, Sep 18, 2015 at 11:44 AM, Reindl Harald 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 > Actually I meant that teamd should have

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

On Fri, Sep 18, 2015 at 4:44 PM, Reindl Harald 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