I have the same experience as described in the original bug description. My system is running
on ubuntu 16.04 and I've installed `nfs-common` (client-only, I don't want `nfs-server` on the system).
# systemctl -a list-unit-files *idmap*
UNIT FILE STATE
idmapd.service masked
nfs-idmapd.service static
I have the same experience as described in the original bug description. My system is running
on ubuntu 16.04 and I've installed `nfs-common` (client-only, I don't want `nfs-server` on the system).
# systemctl -a list-unit-files *idmap*
UNIT FILE STATE
idmapd.service masked
nfs-idmapd.service static
# systemctl status nfs-idmapd -l system/ nfs-idmapd. service; static; vendor preset: enabled)
● nfs-idmapd.service - NFSv4 ID-name mapping service
Loaded: loaded (/lib/systemd/
Active: inactive (dead)
And starting does not work:
# systemctl start nfs-idmapd
Failed to start nfs-idmapd.service: Unit nfs-server.service not found.
Do I understand you, @pitti in #11 correctly that `nfs-server` needs to be installed?
thanks for clarifying!
andi