Date: Thu, 30 Oct 2014 13:32:30 +0100 From: <rank1seeker@gmail.com> To: Allan Jude <allanjude@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: tar behavior 9.* -> 10.* Message-ID: <20141030133230.00004204@gmail.com> In-Reply-To: <544A6595.2070204@freebsd.org> References: <20141024141552.000048ac@gmail.com> <544A6595.2070204@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 24 Oct 2014 10:43:33 -0400 Allan Jude <allanjude@freebsd.org> wrote: > On 2014-10-24 08:15, rank1seeker@gmail.com wrote: > > https://forums.freebsd.org/threads/tar-errors-when-file-content-extracted-to-stdout-is-piped.48626/ > > > > Bug? > > _______________________________________________ > What happens if you pipe it to something that doesn't close the pipe > prematurely > > try: > > tar ... | cat - > > It makes sense that it throws an error when you pipe to head, which > then closes the pipe before the file has finished being written. > Even in it's "cleanest form" it hangs: # tar -xOf src.txz usr/src/UPDATING Outputed complete content immidieatly to STDOUT and then hanged for 56 seconds! With your code situation is same. To cut it short, this is a non critical bug fixed in 9.*, aka tar regression.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141030133230.00004204>