Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 17 Nov 2004 14:17:07 +1100 (EST)
From: Luke Kendall <luke DOT kendall AT cisra DOT canon DOT com DOT au>
Subject: Re: Problem with setup
To: cygwin AT cygwin DOT com
In-Reply-To: <20041117013157.0D785837CA@pessard.research.canon.com.au>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Message-Id: <20041117031707.4D287837CA@pessard.research.canon.com.au>

I should also add that after a setup.exe crash at 9:38am after being
left running overnight, later attempts to install that day (with the VM
size steadily increasing, and setup.exe appearing to "stick" at the
stage where it is installing the zip package), that setup.log was not
updated by the later installation attempts.

Shouldn't setup.log be getting opened in append mode?  We examined it
at various times during a later installation attempt, and the contents
didn't change and the file modification time stayed at 9:38am.

luke


--
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/