On Tue, 6 Dec 2016 15:15:12 +0100 Riccardo Murri <riccardo.murri@gmail.com> wrote: > > Package: nfs-kernel-server > Version: 1:1.2.8-9 > > The systemd service unit file for `nfs-kernel-server` incorrectly > reports the service status as "active" even when the NFS server is *not* > running (e.g., empty exports file). .. > debian@debian-nfs-bug:~$ sudo systemctl status nfs-kernel-server.service > * nfs-kernel-server.service - LSB: Kernel NFS server support > Loaded: loaded (/etc/init.d/nfs-kernel-server) > Active: active (exited) since Tue 2016-12-06 12:12:58 UTC; 1min 36s ago > > Dec 06 12:12:58 debian-nfs-bug nfs-kernel-server[1544]: Not starting NFS kernel daemon: no exports. ... (warning). > Dec 06 12:12:58 debian-nfs-bug systemd[1]: Started LSB: Kernel NFS server support. > Dec 06 12:14:33 debian-nfs-bug systemd[1]: Started LSB: Kernel NFS server support. The problem is, that nfs-kernel-server in jessie is a sysv init script. For those, systemd creates a wrapper unit which uses RemainAfterExit=yes as systemd can not know, if the init script starts a long running process or not. (that's why it shows "active (exited)" instead of "active (running)") The obvious solution is to use a native .service file, where you can set the proper Type=. This is the case for stretch. For jessie, that change would most likely be too invasive though, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature