Hi, stable 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 patches.....10....20... done. Applying patches... done. Fetching 3 new ports or files... done. sort: write failed: standard output: Broken pipe sort: write error Removing old files and directories... done. sudo make -C /usr/ports/converters/ascii2binary: ===> Patching for ascii2binary-2.13_2 ===> Applying FreeBSD patches for ascii2binary-2.13_2 ===> ascii2binary-2.13_2 depends on shared library: intlgrep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe - found ===> Configuring for ascii2binary-2.13_2 Does anyone know something about this issue? -- Adios
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 <spam@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 metadata patches... done. > Applying metadata patches... done. > Fetching 0 metadata files... done. > Fetching 27 patches.....10....20... done. > Applying patches... done. > Fetching 3 new ports or files... done. > sort: write failed: standard output: Broken pipe > sort: write error > Removing old files and directories... done. > > sudo make -C /usr/ports/converters/ascii2binary: > ===> Patching for ascii2binary-2.13_2 > ===> Applying FreeBSD patches for ascii2binary-2.13_2 > ===> ascii2binary-2.13_2 depends on shared library: intlgrep: writing > output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > - found > ===> Configuring for ascii2binary-2.13_2 > > Does anyone know something about this issue? > > > -- > Adios > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
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 broke sh. -- Adios
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 patches.....10....20... done. > Applying patches... done. > Fetching 3 new ports or files... done. > sort: write failed: standard output: Broken pipe > sort: write error > Removing old files and directories... done.> sudo make -C /usr/ports/converters/ascii2binary: > ===> Patching for ascii2binary-2.13_2 > ===> Applying FreeBSD patches for ascii2binary-2.13_2 > ===> ascii2binary-2.13_2 depends on shared library: intlgrep: writing output: Broken pipe > grep: writing output: Broken pipe[snip repetition]> - found > ===> Configuring for ascii2binary-2.13_2> Does anyone know something about this issue?This looks more like the absence of SIGPIPE than an inappropriate SIGPIPE. I can reproduce both of those error messages by running the commands with SIGPIPE ignored. grep(1) seems to behave strangely on write errors, not aborting, for example yes | { trap '' PIPE; grep -v foo; echo $? >&2; } | : prints an endless stream of error messages. Note that sh(1) silently ignores attempts to change the disposition of signals that were ignored on entry to the shell, so a trap - PIPE is unlikely to help you. Similarly, SIGPIPE may be blocked (masked). Few programs expect this. The -i and -j options in procstat should be helpful in finding what exactly is wrong with SIGPIPE. (These options are relatively new, but should be in 8.1.) -- Jilles Tjoelker
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 disappeared.> > -- > Adios > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"