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:	Fri, 11 Feb 2005 10:35:08 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: more ctime bugs
Message-ID:	<20050211093508.GB27256@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<020920052127 DOT 27398 DOT 420A803A0009BD7500006B0622007507440A050E040D0C079D0A AT comcast DOT net>
Mime-Version:	1.0
In-Reply-To:	<020920052127.27398.420A803A0009BD7500006B0622007507440A050E040D0C079D0A@comcast.net>
User-Agent:	Mutt/1.4.2i

Eric,

On Feb  9 21:27, ericblake AT comcast DOT net wrote:
> Corinna, since you've been fixing so many ctime bugs lately to match SUSv3
> and POSIX, could you also fix open(2) when O_TRUNC is set, and write(2) and
> link(2) in general, to touch ctime?

No problem with open and link, but I'm a bit reluctant to do this in
write.  Setting the file time on each WriteFile looks like a pretty
time consuming operation, so I'm a bit in doubt if every write operation
should be slowed down by this, POSIX compatibility or not.  Wouldn't
it help in most cases, if the close after write sets the ctime?


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com Red Hat, Inc.

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