Date: Tue, 20 Jul 2010 18:38:10 +1000 From: Sean <sean@gothic.net.au> To: Ruben van Staveren <ruben@verweg.com> Cc: freebsd-stable@freebsd.org Subject: Re: SIGEPIPE after update to 8.1-RC2 Message-ID: <A01515C1-F521-4314-95F4-3A46023C2619@gothic.net.au> In-Reply-To: <337E2BDC-1A76-40E4-868D-8B403742151C@verweg.com> References: <20100717152455.GA61987@ravenloft.kiev.ua> <4C4264F1.4010708@gothic.net.au> <337E2BDC-1A76-40E4-868D-8B403742151C@verweg.com>
index | next in thread | previous in thread | raw e-mail
On 20/07/2010, at 5:19 PM, Ruben van Staveren wrote: > Hi, > > This happens during a "sudo portupgrade -va --batch" > my shell is /bin/tcsh too. When I run "exec bash" after sudo -s and then do the portupgrade the problem doesn't show up. > > To me, this is a clear breakage and should be considered a show stopper issue for 8.1-RELEASE. All shells should be equally supported, especially when they reside in /bin. Is there already an open pr on this ? > No PR from me, and not a chance of a fix to 8.1 at this point, unless it really does cause breakage (not just a message, but actually stops things); the tag has been laid down and would need to be slid forward. It's likely to be either of two things... a bug in sh, that using tcsh highlights because of differing signal setup; or a bug in tcsh that a bug fix in sh highlights. It's a bug that comes and goes in the history of FreeBSD, at least since early 2006 (based on 10 seconds with Google - http://www.linuxquestions.org/questions/*bsd-17/broken-pipe-432167/) > Thanks, > Ruben > >help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A01515C1-F521-4314-95F4-3A46023C2619>