[systemd-devel] umount NFS problem

Lennart Poettering lennart at poettering.net
Fri Apr 5 10:50:14 UTC 2019

On Fr, 05.04.19 12:42, Harald Dunkel (harald.dunkel at aixigo.de) wrote:

> On 4/5/19 12:21 PM, Lennart Poettering wrote:
> > On Fr, 05.04.19 11:53, Harald Dunkel (harald.dunkel at aixigo.de) wrote:
> >
> > >
> > > This is a VNC session, started via crontab @reboot.
> >
> > IIRC debian/ubuntu do not have pam-systemd in their PAM configuration
> > for cron, which means these services are not tracked by
> > logind/systemd, and hence only killed when crond likes to do that.
> >
> > It's a configuration bug in debian/ubuntu.
> >
> No, it was just a sample. Surely systemd is sufficiently stable
> to recover from some lost processes?

Sure, it is. I mean, your system did shutdown in the end, didn't it?
After the timeouts are hit it will go down anyway, ignoring those
left-over processes.

> The point is that rpcbind (and maybe others) are stopped before
> the NFS umounts come up. Hopefully you agree that this is
> unrelated to some cron jobs?

iirc rpcbind is not needed for NFS to work after the mount is
established. if rpcbind is necessary for NFS mounts it should be
ordered before remote-fs.target, so that NFS moutns are shutdown
before rpcbind goes down. But all of that is really something for the
distro to figure out, systemd upstream doesn't really care about NFS
we just provide the hooks so that distros can order their service
files to the right places.


Lennart Poettering, Berlin

More information about the systemd-devel mailing list