public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Robert Collins <rbcollins@cygwin.com>
To: "pbewig@swbell.net" <pbewig@swbell.net>
Cc: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: setup.exe:  Woe is me!
Date: Mon, 28 Apr 2003 01:09:00 -0000	[thread overview]
Message-ID: <1051462151.892.7.camel@localhost> (raw)
In-Reply-To: <01C30C30.4AAB2700.pbewig@swbell.net>

[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]

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
-- 
GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-04-27 16:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-27  9:48 Phil Bewig
2003-04-27 11:25 ` Greg McCrory
2003-04-27 12:14 ` Igor Pechtchanski
2003-04-27 13:10 ` Max Bowsher
2003-04-27 15:30   ` Hannu E K Nevalainen (garbage mail)
2003-04-28  1:09 ` Robert Collins [this message]
2003-04-28  8:04   ` Igor Pechtchanski
2003-04-28  8:59     ` Log-on-spot (was: setup.exe: Woe is me!) Max Bowsher
2003-04-28 13:41     ` setup.exe: Woe is me! Robert Collins
  -- strict thread matches above, loose matches on Subject: below --
2003-04-28  4:48 Phil Bewig
2003-04-27 16:59 Phil Bewig
2003-04-27 16:49 Phil Bewig
2003-04-27 19:17 ` Elfyn McBratney
2003-04-27  8:55 Phil Bewig
2003-04-27  8:54 Phil Bewig
2003-04-27  8:51 Phil Bewig
2003-04-27  8:34 Phil Bewig
2003-04-26 23:45 Phil Bewig
2003-04-27  0:47 ` Max Bowsher
2003-04-27  0:51   ` Igor Pechtchanski
2003-04-27  2:40   ` Martin Gainty
2003-04-26 21:31 Phil Bewig
2003-04-26 21:58 ` Igor Pechtchanski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1051462151.892.7.camel@localhost \
    --to=rbcollins@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=pbewig@swbell.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).