From owner-freebsd-stable@FreeBSD.ORG Thu Jan 17 19:16:47 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD5F516A419 for ; Thu, 17 Jan 2008 19:16:47 +0000 (UTC) (envelope-from dindin@yandex-team.ru) Received: from relanium.yandex.ru (relanium.yandex.ru [213.180.202.105]) by mx1.freebsd.org (Postfix) with ESMTP id 8727313C458 for ; Thu, 17 Jan 2008 19:16:46 +0000 (UTC) (envelope-from dindin@yandex-team.ru) Received: from sepulca.yandex.ru (dhcp250-167.yandex.ru [87.250.250.167]) by relanium.yandex.ru (8.14.1/8.14.1) with ESMTP id m0HItmfv093475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Jan 2008 21:55:49 +0300 (MSK) (envelope-from dindin@yandex-team.ru) Received: from sepulca.yandex.ru (localhost [127.0.0.1]) by sepulca.yandex.ru (8.14.2/8.13.8) with ESMTP id m0HItmfh091400; Thu, 17 Jan 2008 21:55:48 +0300 (MSK) (envelope-from dindin@yandex-team.ru) Received: (from dindin@localhost) by sepulca.yandex.ru (8.14.2/8.13.8/Submit) id m0HItlc3091391; Thu, 17 Jan 2008 21:55:47 +0300 (MSK) (envelope-from dindin@yandex-team.ru) X-Authentication-Warning: sepulca.yandex.ru: dindin set sender to dindin@yandex-team.ru using -f Date: Thu, 17 Jan 2008 21:55:47 +0300 From: Denis Barov To: bushman@freebsd.org Message-ID: <20080117185547.GA85161@sepulca.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline X-Operating-System: FreeBSD sepulca.yandex.ru 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Antivirus: Dr.Web (R) for Mail Servers on relanium.yandex.ru host X-Antivirus-Code: 100000 Cc: stable@freebsd.org Subject: nscd again X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2008 19:16:47 -0000 Hello! I found some strange behaviour of NIS/nscd when NIS in compat mode. In /etc/nsswitch.conf I have: netgroup: cache compat passwd: cache compat group: cache compat #group_compat: cache nis #passwd_compat: cache nis in /etc/nscd.conf: #nscd.conf threads 16 enable-cache passwd yes keep-hot-count passwd 20480 positive-time-to-live passwd 36000 enable-cache group yes keep-hot-count group 20480 positive-time-to-live group 36000 enable-cache group_compat yes keep-hot-count group_compat 20480 positive-time-to-live group.byname 36000 enable-cache passwd_compat yes keep-hot-count passwd_compat 20480 positive-time-to-live passwd_compat 36000 enable-cache netgroup yes keep-hot-count netgroup 20480 positive-time-to-live netgroup 36000 But, when I do some actions on NIS-client host (host with ypbind), host ignoring cached data. In ypserv debug log: ... ypserv: retrieving next key, previous was: [XXX] ypserv: result of lookup: key: [XXXXXXXXX] data: [XXXXXX:*:1168:] ypserv: procedure ypproc_next called from XXX.XXX.XXX.XXX:739 ypserv: client is referencing map "group.byname". ypserv: retrieving next key, previous was: [XXXXXXXXXXX] ypserv: result of lookup: key: [baytin] data: [XXXXXX:*:1220:] ypserv: procedure ypproc_next called from XXX.XXX.XXX.XXX:739 ypserv: client is referencing map "group.byname". ypserv: retrieving next key, previous was: [XXXXXX] ypserv: result of lookup: key: [XXXX] data: [XXXX:*:3012:] ypserv: procedure ypproc_next called from XXX.XXX.XXX.XXX:739 ypserv: client is referencing map "group.byname". ypserv: retrieving next key, previous was: [XXXX] ypserv: result of lookup: key: [XXX] data: [XXX:*:3021:] ypserv: procedure ypproc_next called from XXX.XXX.XXX.XXX:739 ypserv: client is referencing map "group.byname". ypserv: retrieving next key, previous was: [XXX] ypserv: result of lookup: key: [vereschagin] data: [XXXXXXXXXXX:*:3024:] ypserv: procedure ypproc_next called from XXX.XXX.XXX.XXX:739 ypserv: client is referencing map "group.byname". ypserv: retrieving next key, previous was: [XXXXXXXXXXX] ... If I set in nsswitch.conf: netgroup: cache compat passwd: cache compat group: cache compat group_compat: cache nis passwd_compat: cache nis I have other errors: Jan 17 21:53:13 mfas002 sudo: NSSWITCH(nss_method_lookup): cache, passwd_compat, setpwent, not found Jan 17 21:53:15 mfas002 sudo: NSSWITCH(nss_method_lookup): cache, group_compat, setgrent, not found Jan 17 21:53:15 mfas002 sudo: NSSWITCH(nss_method_lookup): cache, group_compat, getgrent_r, not found Jan 17 21:53:15 mfas002 last message repeated 197 times Jan 17 21:53:15 mfas002 sudo: NSSWITCH(nss_method_lookup): cache, group_compat, endgrent, not found Jan 17 21:53:15 mfas002 sudo: NSSWITCH(nss_method_lookup): cache, passwd_compat, endpwent, not found Jan 17 21:53:15 mfas002 sudo: NSSWITCH(nss_method_lookup): cache, group_compat, endgrent, not found Seems group_compat and passwd_compat databases can't operate with cache sourse. Is that true? -- Denis Barov | /"\ Yandex WEB-Search Administration Team | \ / ASCII Ribbon Campaign phone: : +7 (495) 739-70-00 add. 7154 | X NO HTML/RTF in e-mail e-mail: dindin@yandex-team.ru | / \ NO Word docs in e-mail