I just wrestled with the same problem. I had just stubbed the test out; thanks for the better fix.
A related bug (in the nfs-common package) is that the error message if idmapd is started but nfsv4 support is not enabled is a bit alarming; I spent a while trying to fix it before discovering that the kernel-server startup message had nothing to do with it. Perhaps idmapd could have a special return code for the "no kernel support" case? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
