From owner-freebsd-stable@FreeBSD.ORG Sun Jul 25 11:48:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D09F106564A for ; Sun, 25 Jul 2010 11:48:18 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id 3D7098FC0A for ; Sun, 25 Jul 2010 11:48:18 +0000 (UTC) Received: from turtle.stack.nl (turtle.stack.nl [IPv6:2001:610:1108:5010::132]) by mx1.stack.nl (Postfix) with ESMTP id 4436035A835; Sun, 25 Jul 2010 13:48:16 +0200 (CEST) Received: by turtle.stack.nl (Postfix, from userid 1677) id 2DDED172B8; Sun, 25 Jul 2010 13:48:16 +0200 (CEST) Date: Sun, 25 Jul 2010 13:48:16 +0200 From: Jilles Tjoelker To: Sean Message-ID: <20100725114816.GA78541@stack.nl> References: <20100717152455.GA61987@ravenloft.kiev.ua> <4C4264F1.4010708@gothic.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C4264F1.4010708@gothic.net.au> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: SIGEPIPE after update to 8.1-RC2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2010 11:48:18 -0000 On Sun, Jul 18, 2010 at 12:20:33PM +1000, Sean wrote: > I'm getting the same thing; what shell are you using? I changed my shell > on one machine from /bin/tcsh to /usr/local/bin/bash and problem > disappeared. That this workaround helps confirms that masked/ignored SIGPIPE is the problem. From a few shells I have tried, bash and zsh reset SIGPIPE to caught or default even if it was ignored (only in interactive mode, however), while tcsh, sh, mksh and ksh93 leave it ignored. The underlying problem is the program that is passing the ignored/masked signal to child processes. Please check if the problem occurs with various ways to log in (text console, ssh, xterm, etc). Things like PAM modules may also cause problems here. For example, sshd sets SIGPIPE to ignored, but resets it back to default before starting a child process, so assuming I read the code correctly it does not cause problems. -- Jilles Tjoelker