From owner-freebsd-hackers Tue Aug 22 14:40:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id E9E2637B422 for ; Tue, 22 Aug 2000 14:40:53 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7MLeaT45194; Tue, 22 Aug 2000 14:40:37 -0700 (PDT) Date: Tue, 22 Aug 2000 14:40:36 -0700 (PDT) From: Doug White To: Hajimu UMEMOTO Cc: n@nectar.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Testers wanted: nsswitch In-Reply-To: <20000823.020859.74674005.ume@mahoroba.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Aug 2000, Hajimu UMEMOTO wrote: > >>>>> On Sat, 19 Aug 2000 16:30:17 -0500 > >>>>> "Jacques A. Vidrine" said: > > n> I've made a port of NetBSD's nsswitch code. This allows one to > n> configure various databases such as passwd(5) to use files, NIS, > n> or Hesiod. > > I like bringing nsswitch into FreeBSD. It will reduce maintainance > cost around resolver related routins. > When I merged KAME effort around fixing DNS query order problem from > NetBSD, I was forced to work with nsswitch -> host.conf issue. I think we all like the semantics, but I recall a large discussion about a year ago that NetBSD's nsswitch is serializing, which for heavy DNS use is a major performance hit. I don't recall if a design ever came out of it. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message