Bug#644948: nfs-common: Wrong uid/gid with latest version using NFSv4

[Anders Boström <anders@netinsight.net>]

>>>>> "JH" == Jamie Heilman <jamie@audible.transient.net> writes:

 JH> Anders Boström wrote:
 >> >>>>> "SW" == Stephan Windmüller <windy@white-hawk.de> writes:
 >> 
 SW> On 23.10.2011 13:49, Jamie Heilman wrote:
 >> >> Chances are you all have your nfsidmap Domain mismatched between
 >> >> client and server; check your user.* syslog logs on the client for
 >> >> messages like: nfsidmap: nss_getpwnam: name 'foo@bar' does not map
 >> >> into domain 'baz'

Sorry for the late respons... I've got time to test this again, and it
is indeed a domain-problem. However, I don't get any nfsidmap-messages
in the client syslog, but I do in the server. If I reconfigure my
client idmapd.conf to 'Domain = localdomain' it works as expected. If
I use the default idmapd.conf from nfs-common 1:1.2.5-2+b1 it does not
work.

The server is in this case using the default idmapd.conf from
nfs-common 1:1.2.2-4. And doing any change on the server regarding the
domain-configuration will break a lot of clients, all running NFSv4
using Debian stable, Ubuntu etc. Soo it is a no-go.

Also I don't understand how I'm supposed to configure this. I have
another client in another domain. It is supposed to mount NFS
from it's own domain *and* from our server. If 'Domain = localdomain'
is configured in all places, it works, but I how is this
supposed to be configured???

/ Anders