From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 7 07:13:19 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BF28106566B; Fri, 7 Oct 2011 07:13:19 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 4AD578FC18; Fri, 7 Oct 2011 07:13:19 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p977DIrm024799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Oct 2011 00:13:18 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p977DI0A024798; Fri, 7 Oct 2011 00:13:18 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA00289; Fri, 7 Oct 11 00:06:40 PDT Date: Fri, 07 Oct 2011 07:05:48 -0700 From: perryh@pluto.rain.com To: ivoras@freebsd.org Message-Id: <4e8f073c.3g2aD/Zz9KdsWOKN%perryh@pluto.rain.com> References: <20111004160043.GA16034@lpthe.jussieu.fr> <051853CE-03EC-4EEC-A5AC-C380131B28E4@gsoft.com.au> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-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: Fri, 07 Oct 2011 07:13:19 -0000 Ivan Voras wrote: > On 05/10/2011 09:38, Trond Endrest??l wrote: > > On Wed, 5 Oct 2011 12:54+1030, Daniel O'Connor wrote: > >> In my experience ncsd seems to cache negative hits forever, > >> regardless of the setting for negative-time-to-live. > > > > I'm glad to see I'm not the only one who has noticed this odd > > behaviour of nscd. Shame on me for not speaking up sooner, but > > I feared I might be proved wrong (again), and yes, that's a > > lame excuse. :-/ > > +1. > > It's very annoying when installing ports which add users - the > port adds it then in some future code checks it and it fails. > I've noticed it with at least CUPS. Sounds as if there ought to be a unified mechanism for ports to use when adding users, so that necessary notifications -- e.g. restarting nscd if it is running -- can be done in a standardized way and any necessary customizations can be done in a single place.