rpcbind lingering on IP no longer specified on command line

Dmitry Morozovsky marck at rinet.ru
Wed Jan 4 11:46:08 PST 2006


On Wed, 4 Jan 2006, Vivek Khera wrote:

VK> I had rpcbind running with on two interfaces like this:
VK> 
VK> rpcbind -h 192.168.100.200 -h 10.0.0.9
VK> 
VK> Now, I changed rpcbind_flags in /etc/rc.conf to just have the first address,
VK> and I restarted rpcbind.  the process list from ps shows it is running like
VK> this:
VK> 
VK> rpcbind -h 192.168.100.200
VK> 
VK> Yet nmap on the other address shows rpcbind is still listening on udp there.
VK> How do I stop that?

As I sometimes looked into this, rpcbind (formely portmap) listens on all 
described addresses via udp *and* an tcp:*.111 - I tried to dig why is this but 
did not succeed much.

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


More information about the freebsd-stable mailing list