Mail Archives: cygwin/2003/06/19/22:28:43
I believe you've put your finger on the problem exactly. Before trashing my
own old cygwin setup, I had just reinstalled w2k myself, ending up with the
same file ownership problems you encountered. So it seems that setup reacts
badly when it cannot overwrite a file.
--dave
----- Original Message -----
From: "Dan Hatton" <dan DOT hatton AT btinternet DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Thursday, June 19, 2003 2:58 PM
Subject: Memleak Apparently Attributable to Cygwin Setup
Upgrading to Setup 2.358 didn't solve the problem, although it did
speed up the process of changing from "All:Default" to "All:Install"Ã,
in the package selection screen. Once again, after 2 hours, Setup was
still on a2ps, and total memory usage had reached ~2GB, although
setup-2.358.exe was only admitting responsibility for ~6MB of it.
Inspired by Dave's comment about the problem disappearing when he
purged everything and started a completely fresh install, I went
hunting to make sure all Cygwin stuff was completely gone before
trying to install again. I found 4 files, and supporting bits of the
C:\cygwin directory tree, still laying around, apparently because they
were owned by another user (actually another incarnation of me,) and
I'd been refused permission to delete them, the first time round.
Once I'd got rid of these, I started Setup 2.358 again, and when I
returned the next morning, I had a lovely new Cygwin system. I think
a full install overnight is decisively faster than 1 package in >2
hours, so I guess things are sorted.
--
Thanks folks
Dan
--
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/
--
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/
- Raw text -