On Mon, Feb 05, 2007 at 06:04:51PM +0100, Pierre HABOUZIT wrote:
> On Thu, Apr 27, 2006 at 08:31:08AM -0400, Jesse W. Hathaway wrote:
> > # apt-get install nscd
> > # ps -ef|grep nscd
> > root 4603 1 0 08:25 ? 00:00:00 /usr/sbin/nscd
> > root 4620 4418 0 08:27 pts/3 00:00:00 grep nscd
> >
> > strace ping -c 1 www.google.com > /tmp/strace 2>&1
> >
> > relevant portion of /tmp/strace:
> >
> > connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
> > close(4) = 0
> > socket(PF_FILE, SOCK_STREAM, 0) = 4
> > fcntl64(4, F_GETFL) = 0x2 (flags O_RDWR)
> > fcntl64(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
> > connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
> > close(4) = 0
> >
> > nscd socket is created at /var/run/.nscd_socket rather
> > than /var/run/nscd/socket
> >
> > creating a symlink at /var/run/nscd/socket to /var/run/.nscd_socket
> > resolves the problem
> >
> > this issue is resolved in unstable, it should either be fixed
> > in stable or noted during the installation
>
> well, except that in my setup, when I do exactly the same as what you
> do my strace has:
>
> connect(4, {sa_family=AF_FILE, path="/var/run/.nscd_socket"}, 110) = 0
>
> which obviously works. I suppose you have something unclean in your
> environment somwhere, and there is absolutely nothing related to nscd
> that changed since 2.3.2.ds1-22 until the -22sarge4 I tested.
>
> Moreover, looking at the libc sources, there is absolutely _no_
> reference to a /var/run/nscd/socket whereas you find:
> nscd/nscd-client.h:35:#define _PATH_NSCDSOCKET "/var/run/.nscd_socket"
>
> That header beeing private, there is absolutely no chance anyone could
> have built against an older version. To me it looks like you have a
> "thing" on your system that is not up to date in your sarge. Given that
> nss modules are often used through dlopen's I suppose that the problem
> is that some things on your machine may have remained linked against an
> earlier version of that or this nss module.
>
> E.g. you should check that if you have a libc6-$(arch) module that
> module has been upgraded as well, and that you restarted every service
> using the libc, your shell included.
>
> As nobody has followuped to that bug for more than a year, I'm closing
> the bug.
>
> please mail control@bugs.debian.org with the stanza:
> --8<-----
> reopen 345168
> thanks
> -->8-----
Okay, alioth was hit by this, and upgrading to 2.3.6.ds1-13 fixed it.
so the bug is indeed fixed.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
Attachment:
pgpiy6X4BdpnI.pgp
Description: PGP signature