[Bug 1557015] Re: idmapd not started by systemd on nfs clients (xenial beta1)

2016-03-14 Thread Steve Langasek
thanks for confirming. closing this report as invalid. ** Changed in: nfs-utils (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557015 Title: idmapd not

[Bug 1557015] Re: idmapd not started by systemd on nfs clients (xenial beta1)

2016-03-14 Thread Sebastian Stark
Ok, my bad. I missed that design change. When something not worked in the beginning I just assumed that the missing idmapd was the problem. Probably got confused by the not yet updated documentation in /usr/share/doc/nfs-common/README.Debian.nfsv4. Checked again: id mapping is indeed working for m

[Bug 1557015] Re: idmapd not started by systemd on nfs clients (xenial beta1)

2016-03-14 Thread Steve Langasek
This is entirely by design. Per upstream, idmapd is not needed on current systems; it is superseded by the kernel upcall interface, configured via /etc/request-key.d/id_resolver.conf to use /usr/sbin/nfsidmap. Please explain why you believe this is not working. ** Changed in: nfs-utils (Ubuntu)