From owner-freebsd-current@FreeBSD.ORG Fri Aug 22 14:29:36 2003 Return-Path: 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 2D7EB16A4BF; Fri, 22 Aug 2003 14:29:36 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F05043FDD; Fri, 22 Aug 2003 14:29:35 -0700 (PDT) (envelope-from richardcoleman@mindspring.com) Received: from c-24-98-233-138.atl.client2.attbi.com ([24.98.233.138] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (Exim 3.33 #1) id 19qJTR-0006pG-00; Fri, 22 Aug 2003 14:29:33 -0700 Message-ID: <3F468B41.8090902@mindspring.com> Date: Fri, 22 Aug 2003 17:29:37 -0400 From: Richard Coleman Organization: Critical Magic, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: kientzle@acm.org References: <3F459D29.2030009@mindspring.com> <20030822054454.GA51245@sunbay.com> <3F462B60.50405@mindspring.com> <20030822155140.GA46768@sunbay.com> <3F465DA5.2040002@acm.org> In-Reply-To: <3F465DA5.2040002@acm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 1ee258965991efcb0865379cdb43356e5e89bb4777695beb702e37df12b9c9ef50dab094351943df6b689c9f0aa96e4d350badd9bab72f9c350badd9bab72f9c cc: "Jacques A. Vidrine" cc: freebsd-current@freebsd.org Subject: Re: status of nsswitch.conf in current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: richardcoleman@mindspring.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Aug 2003 21:29:36 -0000 > Having additional examples in /usr/share/examples/etc > would also be nice. (Ideally, with a comment in > /etc/nsswitch.conf.example pointing to those additional > examples.) At the very least, a copy of the default nsswitch.conf should be in the examples directory. Since I didn't find an example there, I figured the facility was either not fully implemented yet, or broken (otherwise an example would be there). That's the reason I asked on the list in the first place. Since I'm pretty experienced with FreeBSD and it confused me, you can be sure it will confuse others. > I do find Ruslan's logic here a bit peculiar, though. Having > an nsswitch.conf with the default settings should only > "slow things down" by the time needed to parse the file. > Well-written parsers are very fast. I also feel that the logic that this will "slow things down" is a red herring. For many of the common cases (i.e. host name resolution by a remote DNS server) the amount of time to parse the nsswitch.conf will be minuscule relative to the amount of time necessary for to perform the lookup. I would love to know how much overhead parsing the nsswitch.conf adds to a local password lookup. Richard Coleman richardcoleman@mindspring.com