Date: Fri, 5 Oct 2001 07:00:09 -0500 From: Vladimir Egorin <vladimir@math.uic.edu> To: "Georg-W. Koltermann" <gwk@sgi.com> Cc: freebsd-current@freebsd.org Subject: Re: NIS client performance seems very poor under network load Message-ID: <20011005070009.A22036@math.uic.edu> In-Reply-To: <lthzo767cb1.wl@hunter.munich.sgi.com>; from gwk@sgi.com on Fri, Oct 05, 2001 at 09:53:22AM %2B0200 References: <20010928022500.I24843-100000@turtle.looksharp.net> <3BBAD3F3.241A1FEE@dsto.defence.gov.au> <15291.10120.604882.602699@grasshopper.cs.duke.edu> <3BBBE105.9863D667@dsto.defence.gov.au> <15292.24342.741023.939305@grasshopper.cs.duke.edu> <3BBD6015.9EB74634@dsto.defence.gov.au> <lthzo767cb1.wl@hunter.munich.sgi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 05, 2001 at 09:53:22AM +0200, Georg-W. Koltermann wrote: > You know, I have been using and NSD, at work on IRIX. I had trouble > with it, it sometimes wouldn't sync with the nameserver, or would > cease to serve any names until I HUPed it. > > And, seriously, I don't really understand what it's good for. Bind > has been responsible for resolving host names as long as I know. WHY > would anyone want to use NIS for hostname resolution? > > I always configure the resolver to use bind (aka named), and have NIS > resolve passwd, group, alias maps etc. if I need that functionality. > When I'm worried about network load, I run a local named in caching > only mode. Named makes a nice system-wide cache, it is maintained > well, so why bother and write another daemon for that? > > -- > Regards, > Georg. I believe nscd (on solaris at least) caches NIS information only and has nothing to do with named. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011005070009.A22036>