From owner-freebsd-questions@FreeBSD.ORG Mon Jun 16 22:21:58 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5BF537B401 for ; Mon, 16 Jun 2003 22:21:58 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4D8143F75 for ; Mon, 16 Jun 2003 22:21:57 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h5H5Lsl1069073; Tue, 17 Jun 2003 00:21:54 -0500 (CDT) (envelope-from dan) Date: Tue, 17 Jun 2003 00:21:54 -0500 From: Dan Nelson To: Brian Towles Message-ID: <20030617052154.GF64929@dan.emsphone.com> References: <61204.209.163.141.62.1055778497.squirrel@home.towles.com> <1055825671.1015.3.camel@runt.home.towles.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1055825671.1015.3.camel@runt.home.towles.com> X-OS: FreeBSD 5.1-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: FreeBSD-Questions Subject: Re: 4.8 and NIS enabled client spawning listening UDP ports per process X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 05:21:58 -0000 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