more ctime bugs
Fri Feb 18 02:10:00 GMT 2005
On Feb 17 13:31, Corinna Vinschen wrote:
> On Feb 13 04:30, Eric Blake wrote:
> > 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.
I've called touch_ctime in fstat nevertheless. It's a first approximation.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:email@example.com
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin