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

- Raw text -