Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <024001c4ccb3$5d89c9e0$e6ec6f83@robinson.cam.ac.uk>
From: "Max Bowsher" <maxb@ukf.net>
To: "Luke Kendall" <luke.kendall@cisra.canon.com.au>, <cygwin@cygwin.com>
References: <20041117031707.4D287837CA@pessard.research.canon.com.au>
Subject: Re: Problem with setup
Date: Wed, 17 Nov 2004 14:40:04 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
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/