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
Message-ID:	<024001c4ccb3$5d89c9e0$e6ec6f83@robinson.cam.ac.uk>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	"Luke Kendall" <luke DOT kendall AT cisra DOT canon DOT com DOT au>, <cygwin AT cygwin DOT com>
References:	<20041117031707 DOT 4D287837CA AT pessard DOT research DOT canon DOT com DOT au>
Subject:	Re: Problem with setup
Date:	Wed, 17 Nov 2004 14:40:04 -0000
MIME-Version:	1.0
X-Cam-ScannerInfo:	http://www.cam.ac.uk/cs/email/scanner/
X-Cam-AntiVirus:	No virus found
X-Cam-SpamDetails:	Not scanned
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam

Luke Kendall wrote:
> 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.

At the moment, the log files are written to disc in one bulk write when 
setup.exe completes. That's probably not a great design feature.

Max.


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