Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <43578ACD.3020509@byu.net> Date: Thu, 20 Oct 2005 06:17:17 -0600 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: please test: coreutils-5.90-3 References: <20051019171128 DOT GR32583 AT calimero DOT vinschen DOT de> In-Reply-To: <20051019171128.GR32583@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Corinna Vinschen on 10/19/2005 11:11 AM: >>utimes(dest,...); // at this point, timestamp is correct >>fchmod(dest_desc,...); >>close(dest_desc); // oops, timestamp changed > > > Apparently NT overwrites the mtime timestamp on close, as long as write > buffers are not written to disk at that time. Chris had an idea how to > work around that in Cygwin so that it should work in most cases now. > Please try the latest snapshot from http://cygwin.com/snapshots/ Slick trick of searching for an open write descriptor visiting the same file. But it begs the question - why not go one step further and create/export futimes(), so that the application can inform cygwin which descriptor to use, bypassing the search? - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDV4rN84KuGfSFAYARAoLKAJ46dvlPPUImPM544Eu0Ym7lJ2yTWQCgy1t5 X5nNwEDWFp529YvxecUSgA0= =WYeh -----END PGP SIGNATURE----- -- 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/