Hi Arthur, On Tue, Oct 14, 2008 at 12:18:11AM +0200, Arthur de Jong wrote: > nfs-utils-1.1.3/utils/idmapd/idmapd.c:674: > > /* XXX: I don't like ignoring this error in the id->name case, > * but we've never returned it, and I need to check that the client > * can handle it gracefully before starting to return it now. */ > > if (im.im_status == IDMAP_STATUS_LOOKUPFAIL) > im.im_status = IDMAP_STATUS_SUCCESS;
That does not seem to be the root of the problem. I've built nfs-utils with these lines commented out on one of my systems and disabled the workaround in idmapd and the problem persists. > That means that I think the only way to fix this is in the short term is > to remove the LOOKUPFAIL to SUCCESS mangling from idmapd.c (which could > have other side effects) or to apply the workaround as described before. Hmm. Probably the workaround should then be included in the default configuration of idmapd. It seems not to cause any harm and works around these problems and IMHO its unlikely that this can be fixed *properly* for lenny. What do you think about this approach? Shall we ask the NFS maintainers about this change to the default configuration? Best Regards, Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
