From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 5 19:23:05 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54F2C106566B for ; Wed, 5 Oct 2011 19:23:05 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 100628FC12 for ; Wed, 5 Oct 2011 19:23:04 +0000 (UTC) Received: by yxk36 with SMTP id 36so2410708yxk.13 for ; Wed, 05 Oct 2011 12:23:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vJw6qvrwAafia23Qqrsax7oyLvUt0FSkSLnjnSvbEkc=; b=Bxy/AkM2JXO451eyP0V7G9SmZ6UvAlhV/daRVVBx6JtrLe+YDDsytC+o//PfutoFSu GeRmxwfvEiZxCinZgKjVb1jihL5fm6qg2eMRu23umgmavLKxLVPGRwcMcGUIGNAcyNqX k96TjmZtzBG4MmLIfhKG3QF05wo9EjyFYyGHg= MIME-Version: 1.0 Received: by 10.236.186.35 with SMTP id v23mr15946219yhm.80.1317842584176; Wed, 05 Oct 2011 12:23:04 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.236.103.33 with HTTP; Wed, 5 Oct 2011 12:23:04 -0700 (PDT) In-Reply-To: References: <86sjn84wco.fsf@ds4.des.no> <86obxw4s4w.fsf@ds4.des.no> <86fwj84p8i.fsf@ds4.des.no> Date: Wed, 5 Oct 2011 12:23:04 -0700 X-Google-Sender-Auth: NeoRm2aSfIy5p1ECPsxBfnafAlI Message-ID: From: Artem Belevich To: Michael Bushkov Content-Type: text/plain; charset=ISO-8859-1 Cc: =?ISO-8859-1?Q?Dag=2DErling_Sm=F8rgrav?= , hackers@freebsd.org, =?ISO-8859-1?Q?Trond_Endrest=F8l?= Subject: Re: Does anyone use nscd? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2011 19:23:05 -0000 2011/10/5 Michael Bushkov : > 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