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: Wed, 18 May 2005 11:54:08 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Mv after tar in a shell script problems Message-ID: <20050518095408.GP18174@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <428B0B51 DOT CB8FB8A AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <428B0B51.CB8FB8A@dessent.net> User-Agent: Mutt/1.4.2i On May 18 02:30, Brian Dessent wrote: > "Gary R. Van Sickle" wrote: > > > ...and, if I change the mv to a loop which keeps trying if there's a > > failure: > > > > while ! mv dir_name_file.tar.bz2_untars_to new_dir_name; do echo "retrying > > move..."; done > > > > it will eventually work after a few iterations. > > > > I... huh? > > > > I'll brew up a test case, this is nutso. > > The only thing I can think of is that tar exits immediately after > issuing the final write() of the last file, and mv starts up before the > file system has a chance to finish commiting that write to disk. Sounds not convincing. If the OS isn't able to deal with such a basic situation, it's seriously unusable. Windows might have some annoying properties, but it's certainly usable. I'm just running a script which desperatly tries to reproduce the above problem, but it WJFFM: #!/bin/sh while true do tar xvjf foo.tar.bz2 mv foo.dir bar.dir rm bar.dir done Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto: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/