From owner-freebsd-current@FreeBSD.ORG Wed Mar 6 12:29:34 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F0825D00 for ; Wed, 6 Mar 2013 12:29:34 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id B62F57D8 for ; Wed, 6 Mar 2013 12:29:34 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:204:4bff:fe01:de8a] (spaceball.andric.com [IPv6:2001:7b8:3a7:0:204:4bff:fe01:de8a]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 126C45C43; Wed, 6 Mar 2013 13:29:32 +0100 (CET) Message-ID: <513736AC.3030108@FreeBSD.org> Date: Wed, 06 Mar 2013 13:29:32 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20130117 Thunderbird/19.0 MIME-Version: 1.0 To: "Hartmann, O." , FreeBSD Current Subject: Re: r247839: broken pipe - for top, sudo and ports References: <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org> <51364914.2010104@zedat.fu-berlin.de> <51364E8D.5020608@zedat.fu-berlin.de> In-Reply-To: <51364E8D.5020608@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Mar 2013 12:29:35 -0000 On 2013-03-05 20:59, Hartmann, O. wrote: ... > A "truss top" reveals this, is this of help? ... > socket(PF_LOCAL,SOCK_STREAM,0) = 4 (0x4) > connect(4,{ AF_UNIX "/var/run/nscd" },15) = 0 (0x0) > fcntl(4,F_SETFL,O_NONBLOCK) = 0 (0x0) ... > sendmsg(0x4,0x7fffffffd290,0x0,0x1,0x1,0x0) ERR#32 'Broken pipe' Maybe your nscd might have died? It is successfully opening and connecting to nscd's unix socket, but gets an EPIPE when it tries to send data.