X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-4.0 required=5.0 tests=AWL,BAYES_05,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
Message-ID:	<503B9803.9080202@gmail.com>
Date:	Mon, 27 Aug 2012 23:53:39 +0800
From:	KHMan <keinhong AT gmail DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: gzip 1.4-1 creates corrupt archive
References:	<98106E7FBCC84B84880593C9916C9502 AT AMIGIME> <CAMK_jUVCdAt6jgCO3MVJzG4AfgTbiH8pQVesLbVheGn63hLeYg AT mail DOT gmail DOT com> <50398B4C DOT 3050000 AT cs DOT utoronto DOT ca> <CAMK_jUVfd5ZR9JjWpEGqyTfoR7DBTM45wmS7kQ79R8N7G9-7kQ AT mail DOT gmail DOT com> <CA+sc5m=a0oS0UHCyjAWgDJTaZEgnURdg7qcVYjwfnTp8p1N8Kw AT mail DOT gmail DOT com> <503B619C DOT 7000700 AT cs DOT utoronto DOT ca>
In-Reply-To:	<503B619C.7000700@cs.utoronto.ca>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 8/27/2012 8:01 PM, Ryan Johnson wrote:
> On 27/08/2012 7:29 AM, Earnie Boyd wrote:
>> On Sun, Aug 26, 2012 at 12:38 AM, K Stahl wrote:
>>> [snip snip snip]
>> [snip snip snip]
> [snip snip snip]
>
> Back on topic, I can't repro using text or binary (executable)
> files, which makes me wonder whether the issue is the constant
> appending the OP mentioned. Perhaps gzip reads twice from the
> growing log file in a way that confuses it, and bzip2 doesn't?
> Perhaps there's some weirdness with atimes that makes gzip think
> the file is unchanged when it actually has grown?

Same for me on text and binary files. I think OP should test 
non-updated text and binary files, that would certainly help to 
prove or disprove some theories.

Also failed to create a corrupted gzip file by manually appending 
from another terminal during compression. After all, gzip is 
reading from stdin only what it gets from cat, and gzip has been 
handling stdin/stdout since forever. Sounds simple enough...

OP gave (reproduced as follows):
 > To trim a log file on my windows box I tried the lines
 > below in a bash script. (my bash is 4.1.10(4))

cat "$LOG" | gzip > "$LOG.old.gz"
 > "$LOG"

What was the error message reported by gzip for the corrupted 
file? gzip has a very simple file structure, if OP can share a 
corrupt file, it should be pretty easy to learn exactly what 
aspect of the gzip file is broken.

-- 
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -