What argument are you passing to rpcinfo?
That info was from tirpc (rpcbind) and a modified nfsd(8) which
was originally ported from NetBSD and adapted to our nfsd(8):
http://home.teleport.ch/freebsd/newnfsd.c
It seems our way doing the registration was wrong (but only for
doing bindhost
Hi,
nfsd.c has the following lines:
(void)signal(SIGQUIT, SIG_IGN);
(void)signal(SIGTERM, SIG_IGN);
So nfsd(8) can only be killed by -9. Does this make
sense ? Unregistering withing rpcbind or portmap is
not possible, so one has to kill portmap(8) or rpcbind(8)
and restart all the rpc
* Martin Blapp [EMAIL PROTECTED] [010225 11:44] wrote:
Hi,
nfsd.c has the following lines:
(void)signal(SIGQUIT, SIG_IGN);
(void)signal(SIGTERM, SIG_IGN);
So nfsd(8) can only be killed by -9. Does this make
sense ? Unregistering withing rpcbind or portmap is
not possible, so one
:
:
:Hi,
:
:nfsd.c has the following lines:
:
:(void)signal(SIGQUIT, SIG_IGN);
:(void)signal(SIGTERM, SIG_IGN);
:
:So nfsd(8) can only be killed by -9. Does this make
:sense ? Unregistering withing rpcbind or portmap is
:not possible, so one has to kill portmap(8) or rpcbind(8)
:and restart all
Hi Matt,
thank you for you mail.
nfsd sits in the kernel most of the time. It needs
to ignore SIGTERM in order to stay alive as long
as possible during a shutdown, otherwise loopback
mounts will not be able to unmount.
ok, added a comment about this.
nfsd -r is used
: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
