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: Thu, 17 Feb 2005 13:31:25 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: more ctime bugs
Message-ID: <20050217123125.GT2597@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> <20050211093508 DOT GB27256 AT cygbert DOT vinschen DOT de> <420CBCE6 DOT 60603 AT byu DOT net> <20050211142542 DOT GE2597 AT cygbert DOT vinschen DOT de> <loom DOT 20050213T052458-195 AT post DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <loom.20050213T052458-195@post.gmane.org>
User-Agent: Mutt/1.4.2i

On Feb 13 04:30, Eric Blake wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > I'll update Cygwin to set ctime in close and link.  Link
> > is special since it doesn't involve using any explicit file descriptors,
> > so it's a bit unclear where to set the flags inside Cygwin to get that
> > right.  Using close() seems a good way to have ctime set for write()
> > as well as open(O_TRUNC).
> 
> I see the new has_changed flag in the 20050211 snapshot.  But you still have to
> add a call to touch_ctime() within the stat() family of calls if has_changed is
> set, in order to comply with the required semantics; stat and lstat are not
> allowed to return out-of-date timestamps.

You know that this contradicts the target to maintain speed on write?
It's not done with adding a call to touch_ctime() to fstat, because
that only affects the application which also has written to the file.
If I read SUSv3 correctly, any call to stat/fstat/lstat on the file
by any application would require to update the timestamp.  That's no
fun.  I'm willing to simply ignore this.


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/