Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Tue, 18 Apr 2000 00:26:13 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: rename() is sometimes unsafe on remote drives. Message-ID: <20000418002613.A5519@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: <20000417205014 DOT A5050 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: ; from fujieda@jaist.ac.jp on Tue, Apr 18, 2000 at 11:49:19AM +0900 On Tue, Apr 18, 2000 at 11:49:19AM +0900, Kazuhiro Fujieda wrote: >>>> On Mon, 17 Apr 2000 20:50:14 -0400 >>>> Chris Faylor said: > >> If, for some reason, the MoveFile of an existing >> file fails, the target file will be gone. rename on UNIX doesn't work >> this way. > >I have never been experienced this case. I tried to create the >case so MoveFile fails and removes the target file, but could >not. Can someone present an example of the case to me? I believe that it's been reported on the mailing list from time to time but maybe your patch was all that was required to fix that. cgf