Re: SIGEPIPE after update to 8.1-RC2

2010-07-28 Thread Kostik Belousov
On Sun, Jul 25, 2010 at 01:48:16PM +0200, Jilles Tjoelker wrote: 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

Re: SIGEPIPE after update to 8.1-RC2

2010-07-25 Thread Jilles Tjoelker
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

Re: SIGEPIPE after update to 8.1-RC2

2010-07-20 Thread Ruben van Staveren
Hi, On 18 Jul 2010, at 4:20, Sean wrote: On 18/07/2010 1:24 AM, Alex Kozlov wrote: Hi, stable After updating my buildbox from 26 April 8-STABLE to 8.1-RC2 I constantly getting SIGEPIPE [snip] I'm getting the same thing; what shell are you using? I changed my shell on one

Re: SIGEPIPE after update to 8.1-RC2

2010-07-20 Thread Jeremy Chadwick
On Tue, Jul 20, 2010 at 09:19:39AM +0200, Ruben van Staveren wrote: To me, this is a clear breakage and should be considered a show stopper issue for 8.1-RELEASE. Too late for that now... ftp://ftp4.freebsd.org/pub/FreeBSD/releases/amd64/ ftp://ftp4.freebsd.org/pub/FreeBSD/releases/i386/ --

Re: SIGEPIPE after update to 8.1-RC2

2010-07-20 Thread Sean
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

Re: SIGEPIPE after update to 8.1-RC2

2010-07-20 Thread Ruben van Staveren
On 20 Jul 2010, at 10:03, Jeremy Chadwick wrote: On Tue, Jul 20, 2010 at 09:19:39AM +0200, Ruben van Staveren wrote: To me, this is a clear breakage and should be considered a show stopper issue for 8.1-RELEASE. Too late for that now… Oh well, errata when the culprit is found… I've filed

Re: SIGEPIPE after update to 8.1-RC2

2010-07-18 Thread Kostik Belousov
On Sun, Jul 18, 2010 at 12:11:50AM +0200, Jilles Tjoelker wrote: On Sat, Jul 17, 2010 at 06:24:55PM +0300, Alex Kozlov wrote: After updating my buildbox from 26 April 8-STABLE to 8.1-RC2 I constantly getting SIGEPIPE portsnap: Fetching 4 metadata patches... done. Applying metadata

Re: SIGEPIPE after update to 8.1-RC2

2010-07-17 Thread Ronald Klop
Try rebuilding bash or sh or whatever you are using as shell. I'm not sure though. Ronald. On Sat, 17 Jul 2010 17:24:55 +0200, Alex Kozlov s...@rm-rf.kiev.ua wrote: Hi, stable After updating my buildbox from 26 April 8-STABLE to 8.1-RC2 I constantly getting SIGEPIPE portsnap: Fetching 4

Re: SIGEPIPE after update to 8.1-RC2

2010-07-17 Thread Alex Kozlov
On Sat, Jul 17, 2010 at 06:58:29PM +0200, Ronald Klop wrote: Try rebuilding bash or sh or whatever you are using as shell. I'm not sure though. I done only preliminary testing, but replacing /bin/sh by one from 8.0-RELEASE seems to help. Thanks. Now I will try to find particular commit that

Re: SIGEPIPE after update to 8.1-RC2

2010-07-17 Thread Jilles Tjoelker
On Sat, Jul 17, 2010 at 06:24:55PM +0300, Alex Kozlov wrote: After updating my buildbox from 26 April 8-STABLE to 8.1-RC2 I constantly getting SIGEPIPE portsnap: Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 27

Re: SIGEPIPE after update to 8.1-RC2

2010-07-17 Thread Sean
On 18/07/2010 1:24 AM, Alex Kozlov wrote: Hi, stable After updating my buildbox from 26 April 8-STABLE to 8.1-RC2 I constantly getting SIGEPIPE [snip] 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