From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 5 05:35:45 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E37B1106566C for ; Wed, 5 Oct 2011 05:35:45 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id AB8C38FC08 for ; Wed, 5 Oct 2011 05:35:45 +0000 (UTC) Received: from lstewart.caia.swin.edu.au (lstewart.caia.swin.edu.au [136.186.229.95]) by lauren.room52.net (Postfix) with ESMTPSA id 3EEC97E84F; Wed, 5 Oct 2011 16:35:44 +1100 (EST) Message-ID: <4E8BECAF.8030204@freebsd.org> Date: Wed, 05 Oct 2011 16:35:43 +1100 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0) Gecko/20110929 Thunderbird/7.0 MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <86sjn84wco.fsf@ds4.des.no> In-Reply-To: <86sjn84wco.fsf@ds4.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lauren.room52.net Cc: hackers@freebsd.org Subject: Re: Does anyone use nscd? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2011 05:35:46 -0000 On 10/05/11 02:20, Dag-Erling Smørgrav wrote: > Does anyone actually use nscd? Yes, particularly for caching LDAP data. > I ask because when I cleaned up a slew of aliasing bugs a couple of > years ago, I believe I may have introduced a bug; I got exactly two > complaints, and neither of the complainants could be bothered to try the > workaround I suggested and report back. I haven't seen these bugs. There is a different bug we hit fairly regularly related to -ve caching. If the machine running nscd loses connectivity with the DNS server for a while and does a DNS lookup during that time, nscd will cache the -ve reply indefinitely for all users, which breaks all sorts of crap. Have to forcibly run "nscd -I all" to fix. I will find and fix this bug one day if noone beats me to it... > Although the code quality is atrocious, nscd is actually a pretty good > idea. I suspect the reason why nobody uses it is that it's off by > default and people simply don't know about it. Besides nuking it, which > would be a shame, we have a range of options, from "just fixing the bug > so those who want to use it can" in one end to "finding someone willing > to clean it up and maintain it and enable it by default" in the other. I'd like to see it stay in base. Moving it (slowly) towards a point where we can turn it on by default would be cool. Cheers, Lawrence