This bug also severely breaks NFSv4 ability to map user id on NFS mounted devices since idmapd is not started unless nfs-common starts which it wont given that users have the default settings in /etc/default/nfs-common because of a flaky detection in the init script whether statd is needed or not. For reasons unknown to me the init script insists on starting statd as long as have NFS mounts listed in fstab even if the file /etc/default/nfs-common clearly state that statd is not needed for NFSv4.
The way to solve this bug is to manually change /etc/default/nfs-common to this: # Do you want to start the statd daemon? It is not needed for NFSv4. NEED_STATD=no -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael <at> rasmussen <dot> cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir <at> datanom <dot> net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir <at> miras <dot> org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- Don't over-comment. - The Elements of Programming Style (Kernighan & Plaugher)
signature.asc
Description: PGP signature
