Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Sun, 27 Apr 2003 15:23:04 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Robert Collins cc: "pbewig AT swbell DOT net" , Subject: RE: setup.exe: Woe is me! In-Reply-To: <1051462151.892.7.camel@localhost> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 28 Apr 2003, Robert Collins wrote: > On Sun, 2003-04-27 at 11:13, 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? > > my WAG: > setup is looping: trying to create a file, failing, and trying again. > > Here's what I'd like you to do: > Check your registry for cygwin mount points, both per user and per > machine. There may be a decompressed cygcheck you can download to do > this. If there isn't, then have a look on this list for other references > to the mount point data. (It's not supported to make registry changes > manually, which is why I'm *not* putting the keys in this email). > > If, as I suspect, you have some broken mount points, just delete the > entire cygwin keys in both user and machine subtrees. > > Now, run setup again, and when you are installing, be very very sure to > install to somewhere like "D:\cygwin", not to "D:\". > > If that doesn't work, then I'll brew up a log-on-the-spot version of > setup.exe for you, which will let us see whats going on. > > Cheers, > Rob Rob, I don't know how much extra effort it'll be, but wouldn't a "log-on-the-spot" command-line option make sense anyway? Or is that what you meant? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT 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 -- 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/