On Fri, Jun 24, 2016 at 1:41 PM, Xin Long <lucien....@gmail.com> wrote: > 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 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 before the network -- to whatever level it might be set up >>> then -- is shut down". >>> That means "After=network.target" can work well. >>> >>> But my situation is opposite to that, I need "a unit that is ordered >>> before network.target will be stopped *after* the network so >>> shutdown". >>> >>> So I added "Before=network.target" to .service file. can it really >>> work as I expect? >>> >> >> No. That is why systemd was forced to introduce additional >> network-pre.target to make it possible to explicitly order things >> before networking is started (or stop after networking has been >> stopped - assuming of course that all services that implement >> networking correct order themselves After network-pre.target). > > So you mean "Before=network-pre.target" can work on my case, right ? >
Yes. >>> I have a service, and want it to be stopped only after network is >>> stopped when system shutdown > > and since which version "network-pre.target" was introduced ? > cause I didn't find it in "man systemd.special" in my system. No idea. It is commit a4a878d04045b46fa9783664e3643a890b356790. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
