rpcbind lingering on IP no longer specified on command line

[Dmitry Morozovsky]

On Wed, 4 Jan 2006, Doug Barton wrote:

DB> > rpcbind -h 192.168.100.200 -h 10.0.0.9
DB> > 
DB> > Now, I changed rpcbind_flags in /etc/rc.conf to just have the first
DB> > address, and I restarted rpcbind.  the process list from ps shows it is
DB> > running like this:
DB> > 
DB> > rpcbind -h 192.168.100.200
DB> > 
DB> > Yet nmap on the other address shows rpcbind is still listening on udp
DB> > there.  How do I stop that?
DB> 
DB> What does 'sockstat | grep rpcbind' tell you?

Mine (from RELENG_6):

marck at chipmunk:/usr/src> sockstat | grep rpc
root     rpcbind    69422 5  stream /var/run/rpcbind.sock
root     rpcbind    69422 6  dgram  -> /var/run/logpriv
root     rpcbind    69422 7  udp4   127.0.0.1:111         *:*
root     rpcbind    69422 8  udp4   10.5.5.2:111          *:*
root     rpcbind    69422 9  udp4   *:621                 *:*
root     rpcbind    69422 10 tcp4   *:111                 *:*
marck at chipmunk:/usr/src> ps ax | grep rpc
69422  ??  Is     0:00.00 rpcbind -h 10.5.5.2
69462  p4  R+     0:00.00 grep rpc
marck at chipmunk:/usr/src> 

Hmmm... I just realized that original question mentions udp, not tcp. However, 
tcp 'listen-to-any' question is still open for me...

Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
------------------------------------------------------------------------