From owner-freebsd-current@FreeBSD.ORG Sun Aug 17 13:25:32 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7B986CAC for ; Sun, 17 Aug 2014 13:25:32 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0BB51281F for ; Sun, 17 Aug 2014 13:25:31 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) with esmtp (envelope-from ) id <1XJ0PT-000LDn-IL>; Sun, 17 Aug 2014 15:22:11 +0200 Received: from g229053128.adsl.alicedsl.de ([92.229.53.128] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) with esmtpsa (envelope-from ) id <1XJ0PT-002tIx-EZ>; Sun, 17 Aug 2014 15:22:11 +0200 Date: Sun, 17 Aug 2014 15:22:02 +0200 From: "O. Hartmann" To: "Eggert, Lars" Subject: Re: nscd not caching Message-ID: <20140817152202.6ec8e374.ohartman@zedat.fu-berlin.de> In-Reply-To: References: Organization: FU Berlin X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/QQj.UnoqZQ/vsLmjjaWO+O4"; protocol="application/pgp-signature" X-Originating-IP: 92.229.53.128 X-ZEDAT-Hint: A Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2014 13:25:32 -0000 --Sig_/QQj.UnoqZQ/vsLmjjaWO+O4 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 17 Aug 2014 13:09:10 +0000 "Eggert, Lars" schrieb: > Nobody using nscd? Really? I can only speak for myself and I stopped using nscd since the support is c= rap. A while ago (t > 1 1/2 years) I realised within a OpenLDAP environment, tha= t when nscd is running, sometimes the system simple "forgets" about root - this is painful= while installing/updating ports and getting interrupted with a weird error "unkno= wn user root". nscd is supposed to be used in large environments where the cost for a user= lookup, like in OpenLDAP, is worse. But obviously FreeBSD isn't used in that large envir= onments with OpenLDAP and I'm wondering what the purpose of nscd is. >=20 > On 2014-8-14, at 13:26, Eggert, Lars wrote: >=20 > > [Resending to current@, since I can't get it to work on -CURRENT either= .] > >=20 > > Hi, > >=20 > > anyone have an idea why nscd would not be caching NIS lookups? > >=20 > > My nsswitch.conf looks as follows: > >=20 > > group: cache files nis > > hosts: cache files dns > > networks: cache files > > passwd: cache files nis > > shells: files > > services: cache files nis > > protocols: cache files > > rpc: cache files > >=20 > > nisdomain is set and ypbind is started, and I see lots of NIS traffic g= oing in and > > out. > >=20 > > But nothing is cached; running nscd with -t just prints this and then t= hen nothing, > > ever: > >=20 > > M1 from main: successfully daemonized > > M1 from main: request agents registered successfully > > M2 from cache: cache was successfully initialized > > M2 from runtime environment: using socket /var/run/nscd > > M2 from runtime environment: successfully initialized > > M1 from main: thread #0 was successfully created > > M1 from main: thread #1 was successfully created > > M1 from main: thread #2 was successfully created > > M1 from main: thread #3 was successfully created > > M1 from main: thread #4 was successfully created > > M1 from main: thread #5 was successfully created > > M1 from main: thread #6 was successfully created > > M1 from main: thread #7 was successfully created > >=20 > > Lars > >=20 >=20 --Sig_/QQj.UnoqZQ/vsLmjjaWO+O4 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJT8KyCAAoJEOgBcD7A/5N8x2sH/0RM0Ehu9vMt3O8qLyAxJi5M 6iyNoldRsM5PWKXl5TkvxpLVGUe7tQSXbKOETu0jaSBJ+CcHIEynEWNVdJ0jlYKu gpp6Yse0f0tpZ1o+007TQlvmoIcT9XQ97jhpIVI89ne94vqImmKvh3eJl7iLcT27 eVWE0oNpK0fbTfZQyT/H9mBF3qopQ1aWBka6SgkCJ7a2el5tZt9CK67eQmDeV+Wh NEYHuSnBqrk0nN7AWPee/w1o88kMrRHNUuf98vAski6fqWe3hgo61mkQhMBrgtXV pQZwtgUMVKoSbSevbAJG8K5qgbrmU6FKXdumm/nq/5XfAeEW+JqQiuk1QBYQF3w= =G1Kf -----END PGP SIGNATURE----- --Sig_/QQj.UnoqZQ/vsLmjjaWO+O4--