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 Date: Thu, 20 Oct 2005 15:21:23 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: please test: coreutils-5.90-3 Message-ID: <20051020132123.GS32583@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20051019171128 DOT GR32583 AT calimero DOT vinschen DOT de> <43578ACD DOT 3020509 AT byu DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43578ACD.3020509@byu.net> User-Agent: Mutt/1.4.2i On Oct 20 06:17, Eric Blake wrote: > -----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? It's not POSIX! But I must admit that it exists on Linux, even though they didn't bother to create a man page for it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader 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/