:ok, added a comment about this.
:
:> nfsd -r is used if you already have nfsd's
:> running but somehow unregistered the nfs service
:> from the portmapper. For example, if you killed
:> the portmapper and restarted it. nfsd -r simply
:> reregisters the service that is already running
:> and then exits.
:
:that's clear. but why I get such output ?
:
:# nfsd -h localhost (and output from rpcinfo(8))
: 100003 2 udp 127.0.0.1.8.1 nfs superuser
: 100003 3 udp 127.0.0.1.8.1 nfs superuser
: 100003 2 udp6 ::1.8.1 nfs superuser
: 100003 3 udp6 ::1.8.1 nfs superuser
:
:and if it's just started normal:
:
:# nfsd(8) and (and output from rpcinfo(8))
: 100003 2 udp 0.0.0.0.8.1 nfs superuser
: 100003 3 udp 0.0.0.0.8.1 nfs superuser
: 100003 2 udp6 ::.8.1 nfs superuser
: 100003 3 udp6 ::.8.1 nfs superuser
:
:Martin
:
:...
If you run nfsd without a -h argument, it binds to INADDR_ANY which
means that it can accept packets from any interface. However, if
you have more then one interface this will break UDP mounts because
the reply packet may not be returned from the same IP address that
it was sent to.
What argument are you passing to rpcinfo? All I get is:
earth:/home/dillon> rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 3 udp 1023 mountd
100005 3 tcp 1023 mountd
100005 1 udp 1023 mountd
100005 1 tcp 1023 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100024 1 udp 1011 status
100024 1 tcp 1022 status
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
The portmapper has no concept of IP address bindings, only port
bindings. It understands program, version, protocol, and port,
and that's it.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message