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

[Andrei Borzenkov]

On Fri, Sep 18, 2015 at 10:44 AM, lucien xin <lucien.xin at gmail.com> 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
> "teamd".
>
> to workaround it, I need to define "After=teamd at team0.service
> teamd at team1.service...."  to the affected service. but that seems
> really stupid. are there better ways so if the service require
> "network.target", systemd will shutdown it before teamd?
>
> is there a way to make "teamd" belongs to "network.target",  or
> another way to meet that requirement?
>

Just order teamd before network.target