Bug#562821: nfs-common: Fails to map user id's via idmapd

Hi statd should be started on both the client and the server if you want locking to work correctly. Have you enabled idmapd in /etc/default/nfs-common? Cheers Luk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas..

Bug#562821: nfs-common: Fails to map user id's via idmapd

This bug report is of course related to version 1.2.1-1 of nfs-common -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C m

Bug#562821: nfs-common: Fails to map user id's via idmapd

Package: nfs-common Version: 1:1.2.0-4.1 Severity: important It seems this version have problem with starting statd which should only be used on a NFS server. An unexpected side effect is that this seems to break id mapping on NFSv4 also. The directories /var/lib/nfs/rpc_pipefs/nfs/clnt0 /var/lib