From owner-freebsd-stable@FreeBSD.ORG Wed Sep 17 21:14:39 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89CDD16A4B3 for ; Wed, 17 Sep 2003 21:14:39 -0700 (PDT) Received: from wally.statscout.com (wally.statscout.com [203.39.101.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1FE843F85 for ; Wed, 17 Sep 2003 21:14:37 -0700 (PDT) (envelope-from pak@statscout.com) Received: from speedy.statscout.com (speedy.statscout.com [10.1.1.100]) by wally.statscout.com (8.11.6/8.11.3av) with ESMTP id h8I4ES711300 for ; Thu, 18 Sep 2003 14:14:29 +1000 (EST) (envelope-from pak@statscout.com) Received: from speedy.statscout.com (localhost.statscout.com [127.0.0.1]) by speedy.statscout.com (8.12.8p1/8.12.8) with ESMTP id h8I4EReM034135 for ; Thu, 18 Sep 2003 14:14:28 +1000 (EST) (envelope-from pak@speedy.statscout.com) Received: from localhost (localhost [[UNIX: localhost]]) by speedy.statscout.com (8.12.8p1/8.12.8/Submit) id h8I4ER8b034134 for stable@freebsd.org; Thu, 18 Sep 2003 14:14:27 +1000 (EST) From: Paul Koch Organization: Statscout To: stable@freebsd.org Date: Thu, 18 Sep 2003 14:14:26 +1000 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309181414.26970.paul.koch@statscout.com> Subject: tar behaviour changed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 04:14:39 -0000 Hi, Observed some behaviour change in tar which caught us out. 4.2 / 4.4-Release: $ tar cfz - . | tar tfz - >/dev/null $ echo $? 0 4.8-Release: $ tar cfz - . | tar tfz - >/dev/null gzip: stdin: decompression OK, trailing garbage ignored tar: Child returned status 2 tar: Error exit delayed from previous errors $ echo $? 2 Did some searching on google/bsd and PRs but couldn't find anything. Looks like when tar is writing to a pipe, it pads to a block size ? Is this normal behaviour now ? Thanks Paul.