Date: Tue, 17 Jun 2003 00:21:54 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Brian Towles <brian@towles.com> Cc: FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: 4.8 and NIS enabled client spawning listening UDP ports per process Message-ID: <20030617052154.GF64929@dan.emsphone.com> In-Reply-To: <1055825671.1015.3.camel@runt.home.towles.com> References: <61204.209.163.141.62.1055778497.squirrel@home.towles.com> <1055825671.1015.3.camel@runt.home.towles.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jun 16), Brian Towles said: > On Mon, 2003-06-16 at 10:48, brian@towles.com wrote: > > Im running a 4.8 Release box as a NIS client and for every process > > that either logs in or changes running as user a Listening UDP port > > is created. > > > > Im putting some sample output from ps sockstat and lsof to show > > what I mean. The problem is these UDP ports are listening ports > > bound to all interfaces. > > > > It appears to be releated to NIS because when i uncomment the > > +::::(etc) from the passwd and group files it goes away for any > > newly started processes. I dont even have to turn off ypbind. > > > > Ive tried to put ypbind in secure mode and well as non broadcast > > mode and the same results happen. > > > > Any ideas as to what this is? More importantly, any idea of how to > > get rid of it? > > This seems to happen in 4.8 Stable as well as Release.. > Any clues? > > Im leaning towards someting in PAM but dont quite know what. This is how NIS client access works. The first NIS lookup creates a UDP socket which is used for the lifetime of the process to talk to the NIS server. They're not listening sockets. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030617052154.GF64929>