[systemd-devel] does "Before=network.target" really work

Hi, I have a service, and want it to be stopped only after network is stopped when system shutdown. I checked "man systemd.special ", network is a special internal service for systemd, , and I found "network.target": "at shutdown, a unit that is ordered after network.target will be stopped

Re: [systemd-devel] does "Before=network.target" really work

On Fri, Jun 24, 2016 at 6:23 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > On Fri, Jun 24, 2016 at 1:11 PM, Xin Long <lucien@gmail.com> wrote: >> Hi, >> >> I have a service, and want it to be stopped only after network is >> stopped whe

Re: [systemd-devel] does "Before=network.target" really work

On Fri, Jun 24, 2016 at 6:22 PM, Michael Hirmke wrote: > Hi Xin, > >>Hi, > >>I have a service, and want it to be stopped only after network is >>stopped when system shutdown. > >>I checked "man systemd.special ", network is a special internal >>service for systemd, , and I

[systemd-devel] does service block when systemctl stop another service

When system shutdown, service [a] try to kill service [b] with 'systemctl stop', but we define the dependence that [b] must die after [a]. Will service [a] block there when system shudown ? ___ systemd-devel mailing list

Re: [systemd-devel] does service block when systemctl stop another service

Hi, Andrei: On Fri, Aug 5, 2016 at 7:13 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > On Fri, Aug 5, 2016 at 2:01 PM, Xin Long <lucien@gmail.com> wrote: >> When system shutdown, service [a] try to kill service [b] with 'systemctl >> stop', >> but we de

Re: [systemd-devel] does service block when systemctl stop another service

Will service [a] block there when system shudown ? >>> >>> Default execution is synchronous, so yes, it will block. >> even stop with "systemctl stop"? it looks kinda stopping manually. >> still check the dependence ? >> >> do you have some way to let it not block, like some params of

Re: [systemd-devel] does service block when systemctl stop another service

> Will service [a] block there when system shudown ? Default execution is synchronous, so yes, it will block. >>> even stop with "systemctl stop"? it looks kinda stopping manually. >>> still check the dependence ? >>> >>> do you have some way to let it not block, like some params of

[systemd-devel] [ISSUE] network block when it kill teamd service with "Before=network-pre.target"

I want teamd.service is stopped after network is stopped when system shutdown, then I add two line in teamd.service as systemd-devel suggests. Before=network-pre.target Wants=network-pre.target But in /etc/sysconfig/network-scripts/ifdown-Team, it also kills teamd with:

Re: [systemd-devel] How to generate core file in system service

On Mon, Sep 25, 2017 at 2:47 PM, Mantas Mikulėnas <graw...@gmail.com> wrote: > On Mon, Sep 25, 2017 at 8:59 AM, Xin Long <lucien@gmail.com> wrote: >> >> Hi, >> >> linux network is using >> systemctl start teamd@team0.service >> to start