I have the same problem as Patrik. Every time my server boots I have to restart nfs-common in order for idmapd to work properly. It appears to be independent of mount attempts from clients. I have been using the same NFS4 setup since dapper with no problems until gutsy, it's pretty simple, one server provides nis, NFS4 shares to both nis clients and one client that doesn't use nis. All clients are affected.
#/etc/exports on server /export 192.168.2.0/24(rw,sync,wdelay,no_subtree_check,fsid=0) /export/mythtv 192.168.2.0/24(rw,sync,wdelay,no_subtree_check,nohide) /export/nishome 192.168.2.0/24(rw,sync,wdelay,no_subtree_check,nohide,no_root_squash) # In /etc/default/nfs-common # An old habit, but autodetection has been problematic NEED_IDMAPD=yes # /etc/idmapd.conf # Same on all local systems [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs # I think this needs to be my NIS domain Domain = mordor.local [Mapping] Nobody-User = nobody Nobody-Group = nogroup [Translation] Method = nsswitch -- idmapping with nfs4 mounts not working in feisty https://bugs.launchpad.net/bugs/106401 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
