From owner-freebsd-bugs Fri Feb 25 15:40: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 293A337BB70 for ; Fri, 25 Feb 2000 15:40:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA44070; Fri, 25 Feb 2000 15:40:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Fri, 25 Feb 2000 15:40:02 -0800 (PST) Message-Id: <200002252340.PAA44070@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: adrian@creative.net.au Subject: Re: bin/9711: Fails: cd /usr/bin; gzip file ; mv file.gz file Reply-To: adrian@creative.net.au Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/9711; it has been noted by GNATS. From: adrian@creative.net.au To: freebsd-gnats-submit@freebsd.org, jhs@freebsd.org Cc: Subject: Re: bin/9711: Fails: cd /usr/bin; gzip file ; mv file.gz file Date: Sat, 26 Feb 2000 07:37:16 +0800 After some investigation, this fails because for files larger than HOWMANY bytes. This happens because it can't pass gzip a full file, and gzip gives a 'unexpected EOF', kills the pipe, and this gives the unexpected read error. The solution for this is a more clever way of unzipping the first part of a file - perhaps gzip's behaviour changed in the past? Jointly hacked on by: Dan Papasian Adrian Chadd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message