Date: Fri, 05 Oct 2001 09:53:22 +0200 From: "Georg-W. Koltermann" <gwk@sgi.com> To: "Thyer, Matthew" <Matthew.Thyer@dsto.defence.gov.au> Cc: Andrew Gallatin <gallatin@cs.duke.edu>, bandix@looksharp.net, current@freebsd.org Subject: Re: NIS client performance seems very poor under network load Message-ID: <lthzo767cb1.wl@hunter.munich.sgi.com> In-Reply-To: <3BBD6015.9EB74634@dsto.defence.gov.au> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. At Fri, 05 Oct 2001 16:54:05 +0930, Thyer, Matthew <Matthew.Thyer@dsto.defence.gov.au> wrote: > > Andrew Gallatin wrote: > > > > Thyer, Matthew writes: > > > So the answer is a name service caching daemon ala nscd on Solaris. > > > > > > > Or linux. Apparently, there is an nscd in glibc. Perhaps somebody > > with motivation could determine if its any good. If so, they could > > chop it out of glibc, make it into a port & add hooks to our libc for > > it. (I no longer work at Duke or even use NIS, so that motivated > > person would not be me). 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?lthzo767cb1.wl>