Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #26361 > unrolled thread

Re: CRC-checksum failed in gzip

Started byLaszlo Nagy <gandalf@shopzeus.com>
First post2012-08-01 16:17 +0200
Last post2012-08-01 16:17 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: CRC-checksum failed in gzip Laszlo Nagy <gandalf@shopzeus.com> - 2012-08-01 16:17 +0200

#26361 — Re: CRC-checksum failed in gzip

FromLaszlo Nagy <gandalf@shopzeus.com>
Date2012-08-01 16:17 +0200
SubjectRe: CRC-checksum failed in gzip
Message-ID<mailman.2829.1343830652.4697.python-list@python.org>
>
> Thanks a lotl, someone that writes on the file while reading might be
> an explanation, the problem is that everyone claims that they are only
> reading the file.
If that is true, then make that file system read only. Soon it will turn 
out who is writing them. ;-)
>
> Apparently this file is generated once and a long time after only read
> by two different tools (in sequence), so this could not be possible
> either in theory.. I'll try to investigate more in this sense since
> it's the only reasonable explation I've found so far.
>
Safe solution would be to develop a system where files go through 
"states" in a predefined order:

* allow programs to write into files with .incomplete extension.
* allow them to rename the file to .complete.
* create a single program that renames .complete files to .gz files 
AFTER making them read-only for everybody else.
* readers should only read .gz file
* .gz files are then guaranteed to be complete.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web