Date: Thu, 5 Jan 2006 10:31:33 -0500 From: Vivek Khera <vivek@khera.org> To: stable@freebsd.org Subject: Re: rpcbind lingering on IP no longer specified on command line Message-ID: <51DD97C7-4002-4459-A709-1B72DC1189A7@khera.org> In-Reply-To: <1136459205.11648.4.camel@buffy.york.ac.uk> References: <A97CE7DE-1841-41D0-B702-E82761FCDD3B@khera.org> <43BC24E7.6090800@FreeBSD.org> <D0C52AF2-A5A9-42BF-8CD8-CFC01235D92C@khera.org> <1136459205.11648.4.camel@buffy.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 5, 2006, at 6:06 AM, Gavin Atkinson wrote: >> Can anyone explain why rpcbind will still bind to all tcp interfaces? > > Although I believe this is a bug, it is actually working as > documented: > > from rpcbind(8): > -h bindip > Specify specific IP addresses to bind to for UDP > requests. Yeah, I noticed that little tiny "UDP requests" note in the -h docs too. There's no reason to bind to all tcp addresses, and it is causing me heartburn for getting the server certified...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51DD97C7-4002-4459-A709-1B72DC1189A7>