NFSv4 without portmapper ? (resent)

[Gabriel Barazer]

Hi,

I am testing the nfs utils (not patched for now) on a clean system (in
fact it's a kind of linux from scratch). I want to write a bootscript
designed to start _only_ the nfsv4 server or a nfsv4 client (without
support for nfsv2/3). Since nfsv4 is designed to operate on only 1 TCP
port, is the portmapper still required ? The 2 only services needed must
be rpc.idmapd and rpc.nfsd, but starting rpc.nfsd appears to hang:
rpc.nfsd command line is :

rpc.nfsd -N 2 -N 3 -U -p 2049 8

strace-ing it show the locations where rpc.nfsd hangs :

open("/proc/fs/nfsd/versions", O_WRONLY) = 4
write(4, "-2 -3 +4 \n", 10)             = 10
close(4)                                = 0
open("/proc/fs/nfsd/portlist", O_RDONLY) = 4
read(4, "", 8192)                       = 0
close(4)                                = 0
open("/proc/fs/nfsd/portlist", O_WRONLY) = 4
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 5
setsockopt(5, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
bind(5, {sa_family=AF_INET, sin_port=htons(2049), 
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
listen(5, 64)                           = 0
[HANGS HERE] write(4, "5\n", 2)                      = -1 EIO 
(Input/output error)

---- then after a timeout and some message on the console (RPC: failed 
to contact portmap, server localhost not responding), it hangs again here :

open("/proc/fs/nfsd/threads", O_WRONLY) = 4
write(4, "8\n", 2)                      = -1 EIO (Input/output error)
close(4)                                = 0

---

I haven't started the portmapper to test how the nfsv4 server behaves 
without it. Since there isn't any port mapping operations required 
neither by the client nor the server, is the behaviour straced above right ?


Thanks,
Gabriel