From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 7 10:30:34 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 CB922106570F for ; Fri, 7 Oct 2011 10:30:34 +0000 (UTC) (envelope-from realbushman@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 853D08FC0A for ; Fri, 7 Oct 2011 10:30:34 +0000 (UTC) Received: by qyk4 with SMTP id 4so3829122qyk.13 for ; Fri, 07 Oct 2011 03:30:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=BA/KoO3Yd6t2uveShNdQY2o/MRwFCh6hMFXTvDQ276A=; b=tNO0oR02yBZ/dr/lgPSTQpgQQUXedlYs9VLeRmWzZNxWPdp+fPY6Si4g3WW95Fjg5g Kmjvp1VDYKS3yWWGryn83KkrJ4VPeKJZpXOfb/bIiODys8a0pictttOsnTnmHbMzJDRz Hpgo6DwtJAegrhxJ42K4OKA+DdhA+r3uisjDk= MIME-Version: 1.0 Received: by 10.229.242.84 with SMTP id lh20mr1407438qcb.211.1317983433741; Fri, 07 Oct 2011 03:30:33 -0700 (PDT) Sender: realbushman@gmail.com Received: by 10.229.8.66 with HTTP; Fri, 7 Oct 2011 03:30:33 -0700 (PDT) In-Reply-To: References: <20111004160043.GA16034@lpthe.jussieu.fr> <051853CE-03EC-4EEC-A5AC-C380131B28E4@gsoft.com.au> <4e8f073c.3g2aD/Zz9KdsWOKN%perryh@pluto.rain.com> Date: Fri, 7 Oct 2011 12:30:33 +0200 X-Google-Sender-Auth: VTg4tTKEWgyikDqLgZIOq4cXews Message-ID: From: Michael Bushkov To: Tom Evans Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, perryh@pluto.rain.com 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 10:30:35 -0000 While I agree that nscd negative caching bug should be fixed, it won't help with the problem that users encounter during ports installation. When, for example, user "x" is added during port install, the following steps are involved: 1. Script checks if "x" is present in the users list. Nscd is queried, it returns negative and caches negative answer. 2. Script adds user "x". 3. Script checks that "x" have indeed been added. Nscd is queried, cachned negative answer is returned. Script fails as a result. So unless negative caching time is less than the time between steps 1) and 3) the issues during ports installation will persist. I like perryh@ idea of fixing it within ports. If we introduce some standard way of adding users/groups then this standard routine can take care of nscd. I don't know how much work this will require though... Cheers, Michael On Fri, Oct 7, 2011 at 11:51 AM, Tom Evans wrote= : > On Fri, Oct 7, 2011 at 3:05 PM, =A0 wrote: >> 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. > > Or nscd fixed to not permanently cache negative hits. Seems more correct. > > Cheers > > Tom > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > >