Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <428B1724.3CE419D7@dessent.net>
Date: Wed, 18 May 2005 03:21:24 -0700
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Mv after tar in a shell script problems
References: <428B0B51.CB8FB8A@dessent.net> <20050518095408.GP18174@calimero.vinschen.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin@cygwin.com

Corinna Vinschen wrote:

> 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:

It just occured to me that some antivirus-type programs hook into file
IO calls.  Perhaps such a program is being invoked to scan the file
after it is created and keeps it open for that brief instant long enough
for mv to try to move it.

Brian

--
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/