From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 95494 invoked by alias); 31 Dec 2017 18:05:10 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 95468 invoked by uid 89); 31 Dec 2017 18:05:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=BAYES_05,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=H*F:D*yandex.ru, H*M:yandex, terrible, HX-Priority:Normal X-HELO: forward103j.mail.yandex.net Received: from forward103j.mail.yandex.net (HELO forward103j.mail.yandex.net) (5.45.198.246) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 31 Dec 2017 18:05:05 +0000 Received: from mxback14j.mail.yandex.net (mxback14j.mail.yandex.net [IPv6:2a02:6b8:0:1619::90]) by forward103j.mail.yandex.net (Yandex) with ESMTP id 69F6534C0AA0; Sun, 31 Dec 2017 21:05:02 +0300 (MSK) Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [2a02:6b8:0:1a2d::28]) by mxback14j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id hbaqFWkeSL-52serF21; Sun, 31 Dec 2017 21:05:02 +0300 Received: by smtp4o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 5VuJ9qS1Z4-516qNh8j; Sun, 31 Dec 2017 21:05:01 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) Authentication-Results: smtp4o.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Sun, 31 Dec 2017 17:57:58 -0000 Date: Sun, 31 Dec 2017 18:30:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <03203565.20171231205758@yandex.ru> To: Amit Choudhary , cygwin@cygwin.com Subject: Re: Question regarding cygwin setup. In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-12/txt/msg00290.txt.bz2 Greetings, Amit Choudhary! > 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. That's not true. All already downloaded packages will not be downloaded again. > 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). Everything is possible. The question is, who would implement it? Are you volunteering? > 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%. Normally, any sane application will terminate socket way before that. -- With best regards, Andrey Repin Sunday, December 31, 2017 20:56:19 Sorry for my terrible english... -- 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