Date: Thu, 07 May 2009 10:51:50 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de> Cc: freebsd-current@freebsd.org, openoffice@freebsd.org Subject: Re: gunzip | tar reports broken pipe during OOO build on amd64. Message-ID: <4A031FB6.2050907@freebsd.org> In-Reply-To: <20090506192603.GA56228@wep4035.physik.uni-wuerzburg.de> References: <20090505174831.GA40305@wep4035.physik.uni-wuerzburg.de> <3GBQgy9AhtC1kpgclCTM4BIxKP8@AbNt2aYVonA6XSQc9As8EVwIk24> <20090506032832.GB45796@wep4035.physik.uni-wuerzburg.de> <92cd2ff70905060501vaaf67bdnaee1be72e04f1ef8@mail.gmail.com> <20090506192603.GA56228@wep4035.physik.uni-wuerzburg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>> Tue, May 05, 2009 at 07:48:31PM +0200, Alexey Shuvaev wrote: >>>>> The reason appeared to be the first part of the command >>>>> "gunzip -c ... | ( tar -xf - ) && touch ..." >>>>> which exited with non-zero exit status (141) and "touch ..." was not >>> called. >>>>> Running the command manually has showed that gunzip was complaining >>> about >>>>> broken pipe (however the archive was extracted successfully). >>>> Yes, 141 means that SIGPIPE was delivered. This in turn means that >>>> 'tar -xf -' exited before gunzip had finished its job and gunzip had >>>> tried to write more data to the pipe. I finally reproduced this; it seems to only happen with /bin/csh. It does not happen with /bin/sh or bash. Also, in /bin/csh, this works: (gunzip -c ooo_crystal_images-1.tar.gz | tar xf -) && echo OK and this fails: gunzip -c ooo_crystal_images-1.tar.gz | (tar xf -) && echo OK Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A031FB6.2050907>