From owner-freebsd-current@FreeBSD.ORG  Tue Apr  8 10:42:19 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4E17837B407
	for <current@freebsd.org>; Tue,  8 Apr 2003 10:42:19 -0700 (PDT)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AEC6643FBD
	for <current@freebsd.org>; Tue,  8 Apr 2003 10:42:18 -0700 (PDT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.9/8.12.9) id h38HgIQL084969;
	Tue, 8 Apr 2003 12:42:18 -0500 (CDT)
	(envelope-from dan)
Date: Tue, 8 Apr 2003 12:42:18 -0500
From: Dan Nelson <dnelson@allantgroup.com>
To: Terry Lambert <tlambert2@mindspring.com>
Message-ID: <20030408174218.GE86482@dan.emsphone.com>
References: <u2sznn19jvw.fsf@gs166.sp.cs.cmu.edu>
	<3E92E509.A7A43986@mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E92E509.A7A43986@mindspring.com>
X-OS: FreeBSD 5.0-CURRENT
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.4i
cc: Dan Pelleg <daniel+bsd@pelleg.org>
cc: current@freebsd.org
Subject: Re: NIS exhausts system resources
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2003 17:42:19 -0000

In the last episode (Apr 08), Terry Lambert said:
> Dan Pelleg wrote:
> > When does this happen, you ask? I triggered it this morning by
> > booting the machine when the NIS server was down. I had also seen
> > it in the past when configuring NIS, and it happened as soon as I
> > set the domainname.  Any ideas? I can provide packet captures on
> > request, however note the failure where the server is down.
> 
> Historical behaviour when the NIS server is down has been for the
> client machines to hang until the NIS server is back up.

I've never seen that here.  I have three NIS servers though, so there
has never been a case when all NIS resources were unavailable.  Usually
what I see in the logs are:

Mar 12 13:52:13 ypbind[113]: NIS server [10.0.0.11] for domain not responding
Mar 12 13:52:13 ypbind[113]: NIS server [10.0.0.89] for domain OK

Was it ypbind that was hogging all the file descriptors, or what, I
wonder?

-- 
	Dan Nelson
	dnelson@allantgroup.com