Re: more ctime bugs

2005-02-17 Thread Corinna Vinschen
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 requir

Re: more ctime bugs

2005-02-17 Thread Corinna Vinschen
On Feb 13 04:30, Eric Blake wrote: > Corinna Vinschen 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.

Re: more ctime bugs

2005-02-12 Thread Eric Blake
Corinna Vinschen 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

Re: more ctime bugs

2005-02-11 Thread Corinna Vinschen
On Feb 11 07:10, Eric Blake wrote: > According to Corinna Vinschen on 2/11/2005 2:35 AM: > > 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 writ

RE: more ctime bugs

2005-02-11 Thread Dave Korn
> -Original Message- > From: cygwin-owner On Behalf Of Eric Blake > Sent: 11 February 2005 14:11 > That idea is close to what I had in mind. Note that POSIX > wording in 4.7 > for updating file times, > http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_cha > p04.html: > There i

Re: more ctime bugs

2005-02-11 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Corinna Vinschen on 2/11/2005 2:35 AM: > 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

RE: more ctime bugs

2005-02-11 Thread Dave Korn
> -Original Message- > From: cygwin-owner On Behalf Of Corinna Vinschen > Sent: 11 February 2005 09:35 > On Feb 9 21:27, ericblake 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

Re: more ctime bugs

2005-02-11 Thread Corinna Vinschen
Eric, On Feb 9 21:27, [EMAIL PROTECTED] 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 t