Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 20 Oct 2005 09:24:00 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: please test: coreutils-5.90-3 Message-ID: <20051020132400.GC26262@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20051019171128.GR32583@calimero.vinschen.de> <43578ACD.3020509@byu.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.5.8i On Thu, Oct 20, 2005 at 06:17:17AM -0600, 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? Corinna, I think I win the bet, right? cgf -- 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/