[systemd-devel] How to keep certain services or mounts active during shutdown?

[Frank Steiner]

Lennart Poettering wrote

> Normally the network mounts should be ordered after network.target,
> and wicked before that. Since in systemd the shutdown order is always
> the inverse of the startup order this would mean that the mounts are
> removed first, and wicked only stopped afterwards.

I guess the problem is the root-over-nfs. On reboot I can see all
the NFS mounts are unmounted, but not / (which is good :-)). Then wicked
stops. It seems the system is not aware of the root fs the way it
gets mounted over nfs(v4) in dracut. I can't find any matching .mount
in /run/systemd or in "systemctl list-dependencies".

> How is that "certaint point" defined? As something like "after service
> foo has been shut down"? If so, then my recommendation above of adding
> RequiresMountsFor= to the service sound like the much better solution.

Sounds semantically better! I'll try that!

cu,
Frank

-- 
Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik    Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17           Phone: +49 89 2180-4049
80333 Muenchen, Germany       Fax:   +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *