X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.6 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
From:	George Barrick <gbarrick AT walsh DOT edu>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Date:	Fri, 12 Mar 2010 13:51:53 -0500
Subject:	Re: incomplete/corrupted setup.exe
Message-ID:	<4B30AD0BED19E842AAE88DC397364931240B83C3EF@mail3.walsh.edu>
MIME-Version:	1.0
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

                   2010.03.12.18:53:51 UT

Hi Larry,

    O.K.  So that would be a 'backbone'
server in my region that caches the file,
but gets a corrupted version of it?

    In that circumstance, it is nothing
"insidious".  I just have to wait until
the offending file gets flushed from the
server.

George             gbarrick AT walsh DOT edu



--
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 -