> ...is it true? It seems like there are some valid concerns about > problems with setup.exe in the cygwin mailing list and no one is > addressing them. > > Setup.exe is too important a piece of the cygwin release for it to > go unsupported. Please, someone (Max?) respond to and, if possible, > investigate claims of problems.
I'll confirm that. I was preparing for a reinstall, so I had all packages downloaded. During the install: - The open handle count for setup.exe was 74 while it was running it's md5 checks. - Maybe a quarter of the way through the install (up to gcc in a full install), there were over 200 open handles. Almost all of them were associated with the tar.bz2 files for the packages, ex: 148: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\antiword\antiword-0.34-2.tar.bz2 14c: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\apr\apr-0.9.5_2.0.52-1.tar.bz2 150: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\apache\apache-1.3.29-2.tar.bz2 154: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\apr-util\apr-util-0.9.5_2.0.52-1.tar.bz2 158: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\ash\ash-20040127-1.tar.bz2 15c: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\aspell\aspell-0.50.3-1.tar.bz2 160: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\aspell\aspell-de\aspell-de-0.50.2-1.tar.bz2 164: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\aspell\aspell-dev\aspell-dev-0.50.3-1.tar.bz2 168: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\aspell\aspell-doc\aspell-doc-0.50.3-1.tar.bz2 16c: File C:\Program Files\Cygwin Setup\ftp%3a%2f%2fmirror.mcs.anl.gov%2fpub%2fcygwin.com\release\aspell\aspell-en\aspell-en-0.51.0-1.tar.bz2 So it looks like the package files aren't being closed somewhere. -Samrobb