4.8 and NIS enabled client spawning listening UDP ports per process

[Dan Nelson]

In the last episode (Jun 16), Brian Towles said:
> On Mon, 2003-06-16 at 10:48, brian at 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 at allantgroup.com