From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20346 invoked by alias); 27 Apr 2003 13:33:42 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 20339 invoked from network); 27 Apr 2003 13:33:41 -0000 Received: from unknown (HELO mta7.pltn13.pbi.net) (64.164.98.8) by sources.redhat.com with SMTP; 27 Apr 2003 13:33:41 -0000 Received: from candy (adsl-64-123-252-103.dsl.kscymo.swbell.net [64.123.252.103]) by mta7.pltn13.pbi.net (8.12.9/8.12.3) with SMTP id h3RDXdMd029256 for ; Sun, 27 Apr 2003 06:33:40 -0700 (PDT) Received: by localhost with Microsoft MAPI; Sun, 27 Apr 2003 08:33:33 -0500 Message-ID: <01C30C97.B05102C0.pbewig@swbell.net> From: Phil Bewig Reply-To: "pbewig@swbell.net" To: "'cygwin@cygwin.com'" Subject: RE: setup.exe: Woe is me! Date: Sun, 27 Apr 2003 16:59:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg02384.txt.bz2 On Saturday, April 26, 2003 8:57 PM, Igor Pechtchanski [SMTP:pechtcha@cs.nyu.edu] wrote: > On Sat, 26 Apr 2003, Phil Bewig wrote: > > > I just killed setup.exe after over an hour of inactivity. A total > > of over 125MB of disk space has disappeared in the last few > > hours while I have been running setup.exe, reading and > > replying to email on the cygwin mailing list in this thread > > using MS Outlook, and searching the cygwin mailing list > > archives with MSIE. When I killed setup.exe (using the > > "cancel" button on the progress screen), I received a popup > > message "Cannot open log file d:\/var/log/setup.log for > > writing." Are there any additional clues here? What is > > consuming disk? And how do I get it back? > > > > Thanks again, > > Phil > > Phil, > > Setup.exe first downloads the tarballs of the Cygwin packages from your > chosen mirror to your local disk, into a subdirectory of the "Local > Installation Directory". If you're on a dial-up connection, it may take > quite a while, depending on the number of packages you chose to install. > Once all the packages are downloaded, setup.exe switches to the > installation phase, where it installs the files contained in those > packages (by unpacking them). The third phase runs whatever postinstall > scripts were in those packages. > > My guess is that the space has been taken up by the local cache directory. > Setup.exe runs in multiple threads. The files are downloaded in a > separate thread from the main thread (that handles Windows messages and > updates the main window). If the main thread is hung, downloads will > still continue, giving the impression of disappearing disk space. The > fact that the "Cancel" button works means that the main thread is not > truly hung, but something is probably screwed up with the sequencing logic > somewhere... It would be really nice to get a gdb backtrace, since it's > so reproducible for you. > Igor > P.S. FYI, larger packages (e.g., tetex) easily run into tens of megabytes > -- > http://cs.nyu.edu/~pechtcha/ > |\ _,,,---,,_ pechtcha@cs.nyu.edu > ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com > |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski > '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! > > Knowledge is an unending adventure at the edge of uncertainty. > -- Leto II I think my situation is different. I have already downloaded the files and am installing from the copy of the *.bz2 files under the d:\package directory. All of the activity should be confined to the d: drive, which has over 900MB free. The space is being consumed on the c: drive. I assume the space is going into the swap file at c:\windows\system\win386.swp, which is currently at 78MB, although I don't know that for sure. I could verify that by resetting the swap file to zero bytes and running setup again, but I don't know how to reset the swap file. Besides the large space consumption on c:, my other question is the error message, which implies a problem writing on d:. There is certainly plenty of space. Does anyone know what combination of events could cause that error message? I said earlier, but it may have been forgotten, that I had cygwin installed on this machine about a year ago. I uninstalled it using the instructions in the faq. Could anything be left over from that old installation that is causing problems now? Many thanks, Phil -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/