Date: Tue, 8 Apr 2003 12:42:18 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Terry Lambert <tlambert2@mindspring.com> Cc: current@freebsd.org Subject: Re: NIS exhausts system resources Message-ID: <20030408174218.GE86482@dan.emsphone.com> In-Reply-To: <3E92E509.A7A43986@mindspring.com> References: <u2sznn19jvw.fsf@gs166.sp.cs.cmu.edu> <3E92E509.A7A43986@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030408174218.GE86482>