Date: Wed, 5 Oct 2011 12:23:04 -0700 From: Artem Belevich <art@freebsd.org> To: Michael Bushkov <bushman@freebsd.org> Cc: =?ISO-8859-1?Q?Dag=2DErling_Sm=F8rgrav?= <des@des.no>, hackers@freebsd.org, =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> Subject: Re: Does anyone use nscd? Message-ID: <CAFqOu6gTojMJZRvoj8fLP5=49j1=hKFK0=_3aVH63c30C3Wczg@mail.gmail.com> In-Reply-To: <CANkaO_F%2BeenvB-GSSJ-iZf8Lzu3TV0pLEokw_OjM-wNRXvHR3Q@mail.gmail.com> References: <86sjn84wco.fsf@ds4.des.no> <alpine.BSF.2.00.1110041800290.18373@mail.fig.ol.no> <86obxw4s4w.fsf@ds4.des.no> <CAFqOu6iw12BbvmS9NH3fNzWqQR1YvYrqyM6JFrYDfs2=HQ3w_w@mail.gmail.com> <86fwj84p8i.fsf@ds4.des.no> <CAFqOu6gf9LW2cRHAerTy5d29WN6y8mcWgUHwbKeAEBPXNwVz-w@mail.gmail.com> <CANkaO_F%2BeenvB-GSSJ-iZf8Lzu3TV0pLEokw_OjM-wNRXvHR3Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/10/5 Michael Bushkov <bushman@freebsd.org>: > There are probably 2 things here: > 1. There's some error in nsswitch<->nscd communication protocol that > causes nsswitch to write into the closed socket. This is not trivial > to investigate and will require analyzing nscd and client process logs > side by side (and possibly adding some more logging). > 2. Consequences of the aforementioned problem can probably be > corrected by using _setsockopt(..., SO_NOSIGPIPE) in > __open_cached_connection() in nscachedcli.c > (http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/net/nscachedcli.c?rev=1.3). > > I have no access to FreeBSD desktop at the moment - Artem, it would be > cool if you can try the second solution. That's exactly what I did and it fixed the problem on the client side. I've posted the patch setting SO_NOSIGPIPE earlier in this thread: http://lists.freebsd.org/pipermail/freebsd-hackers/2011-October/036539.html --Artem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFqOu6gTojMJZRvoj8fLP5=49j1=hKFK0=_3aVH63c30C3Wczg>