Date: Fri, 22 Aug 2003 17:29:37 -0400 From: Richard Coleman <richardcoleman@mindspring.com> To: kientzle@acm.org Cc: freebsd-current@freebsd.org Subject: Re: status of nsswitch.conf in current? Message-ID: <3F468B41.8090902@mindspring.com> In-Reply-To: <3F465DA5.2040002@acm.org> References: <3F459D29.2030009@mindspring.com> <20030822054454.GA51245@sunbay.com> <3F462B60.50405@mindspring.com> <20030822155140.GA46768@sunbay.com> <3F465DA5.2040002@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F468B41.8090902>