Date: Mon, 13 Jul 2009 13:28:13 -0400 From: Michael Proto <mike@jellydonut.org> To: Vlad Galu <dudu@dudu.ro>, freebsd-stable@freebsd.org Subject: Re: pw groupadd/useradd fail when the nscd cache is used for name/group resolution Message-ID: <1de79840907131028n5b8f21deyd968639732c651a4@mail.gmail.com> In-Reply-To: <20090713165717.GN2145@acme.spoerlein.net> References: <ad79ad6b0907090613t78cf8540n5fcd3934cadde526@mail.gmail.com> <20090713165717.GN2145@acme.spoerlein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 13, 2009 at 12:57 PM, Ulrich Sp=F6rlein<uqs@spoerlein.net> wrot= e: > On Thu, 09.07.2009 at 16:13:25 +0300, Vlad Galu wrote: >> I've stumbled upon this while installing postgres. In >> /etc/nsswitch.conf I had "group: cache files compat" and "passwd: >> cache files compat". Once I commented them out things started working >> again. Before the change, this is how it looked like: >> >> -- cut here -- >> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsq= l -g 70 >> pw: group disappeared during update >> [root@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsq= l -g 70 >> pw: group 'pgsql' already exists >> [root@vgalu /usr/ports/databases/postgresql84-server]# >> -- and here -- >> >> Shouldn't 'files' be used upon a cache miss? If this is a PEBKAC, >> sorry for the noise. > > Just a me too. This is most likely because nscd is also caching negative > lookups. The usual workaround would be to restart it using > /etc/rc.d/nscd restart > A slightly lower-impact alternative would be to use "nscd -i passwd" to invalidate the password cache. -Proto
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1de79840907131028n5b8f21deyd968639732c651a4>