This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: setup.exe: Woe is me!
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Robert Collins <rbcollins at cygwin dot com>
- Cc: "pbewig at swbell dot net" <pbewig at swbell dot net>, <cygwin at cygwin dot com>
- Date: Sun, 27 Apr 2003 15:23:04 -0400 (EDT)
- Subject: RE: setup.exe: Woe is me!
- Reply-to: cygwin at cygwin dot com
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/