Package: nfs-common Version: 1:1.3.4-2 Severity: important Dear Maintainer,
looks like startup of nfs-common package via System V init script is not supported anymore in Debian stretch. I'm OK with this, but there seems to be no documentation (/usr/share/doc/nfs-common/README.Debian) on how to startup the rpc services for an nfs-client using native systemd commands. /etc/default/nfs-common does not seem to work anymore. In my case I'm trying to run an nfs4 client (via autofs) which will need rpc.idmapd and rpc.gssd. While I was able to run rpc.gssd using the following command: systemctl start rpc-gssd.service I am unable to run rpc.idmapd. "systemctl start nfs-idmapd.service" gives me the following bogus message: Failed to start nfs-idmapd.service: Unit nfs-server.service not found. Looks very strange to me! systemctl cat nfs-idmapd.service gives: [Unit] Description=NFSv4 ID-name mapping service DefaultDependencies=no Requires=run-rpc_pipefs.mount After=run-rpc_pipefs.mount local-fs.target BindsTo=nfs-server.service Wants=nfs-config.service After=nfs-config.service [Service] EnvironmentFile=-/run/sysconfig/nfs-utils Type=forking ExecStart=/usr/sbin/rpc.idmapd $RPCIDMAPDARGS Thus this seems to require nfs-server.service which is part of nfs-kernel-server, but I do not intend to install this package because I am talking abount an nfs-client machine here not an nfs server. In case of NFS4 rpc.idmapd has to run on both machines, the cleint _and_ the server. So what is the intended way to run rpc.statd, rpc.idmapd and rpc.gssd on an NFS client machine or getting them autostarted when mounting. Regards Sven
