DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=Y8J0yMMreEOwIEMxZrVyjfKH+GSvS
	9iy//Q2pEIulGOOY2m4UyGfa1z5APgEyaitWflTReyqOQEUK5ZtGLV2S7Ny6TqYc
	mB76HZ4BVM6w8YC9rELe1/m8h4zPqlCTjTCuGoBAubhJpUbUrww/2Xs5F89ymwkc
	S49U8lvEe4g2dc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
From: Amit Choudhary <ac7009064 AT gmail DOT com>
Date: Sun, 31 Dec 2017 21:41:26 +0530
Message-ID: <CAPEO9VGg2P_PLc3ihD1RemLDBPLShiXr40h6au5jq1ytbFamqg@mail.gmail.com>
Subject: Question regarding cygwin setup.
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"

Hi,

I have noticed that if cygwin setup is running and it is installing
something then if the network connection goes away, then cygwin setup just
goes back to 0% and starts all over again after network comes back (I have
to start it again).

So, if cygwin setup had completed 90% of installation and then network goes
away then it goes back to 0%. So, all the bandwidth used for 90%
installation went to waste and also the time to go till 90% installation
went to waste.

Is it possible that cygwin setup gets stuck on network rather than going
back to 0% and start again when network connection comes back (Obviously
cygwin setup should not be aborted in between).

Normally, TCP connections stay alive for 2 hours before reset, so I guess
cygwin setup can just block on the TCP socket / connection rather than
going back to 0%.

Amit

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