X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 17 Nov 2007 07:08:43 +0100
From: Thomas Baker <tbaker AT tbaker DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: Reliable old script... AVS problem - RESOLUTION
Message-ID: <20071117060843.GA3240@sub-tombaker>
References: <20071111173033 DOT GA2360 AT sub-tombaker> <fh7ppg$uaa$1 AT ger DOT gmane DOT org> <20071112090628 DOT GA3792 AT sub-tombaker> <fh98d3$ded$1 AT ger DOT gmane DOT org> <20071113165901 DOT GA2096 AT sub-tombaker> <20071114072231 DOT GB252 AT sub-tombaker> <fhftht$hqa$1 AT ger DOT gmane DOT org> <473B7ECE DOT 3080005 AT cygwin DOT com> <20071116094502 DOT GA2172 AT sub-tombaker> <036b01c8283d$1a0a2e10$2e08a8c0 AT CAM DOT ARTIMI DOT COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <036b01c8283d$1a0a2e10$2e08a8c0@CAM.ARTIMI.COM>
User-Agent: Mutt/1.4.2.1i
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Fri, Nov 16, 2007 at 10:40:27AM -0000, Dave Korn wrote:
> On 16 November 2007 09:45, Thomas Baker wrote:
> > I uninstalled Anti-Vir [1], and the script has run hundreds
> > of times on several different data sources with no errors yet,
> > so this may indeed be the problem!
> 
>   There's another one for the list then I guess.  Ouch.  Nothing's worse than
> data loss.

Further testing strongly suggests (so far) that the problem
is indeed caused by Anti-Vir.  The solution, however, appears
to be as simple as configuring Anti-Vir to check files only
upon reading, _not_ upon writing.  (I was going to try AVG,
but that no longer seems necessary.)

Four weeks and three machines later, at least I know now.
Can anyone explain why check-on-write would cause this problem
-- maybe because Anti-Vir was holding up writing to disk
until after the next command in my script had been executed
and had tried to read the file that was not yet written?

Though not a "Cygwin problem" per se, I'm guessing that
other people must have this problem as well - maybe a line
of explanation could be added to future BLODA lists and/or
the Cygwin FAQ.

Many thanks to everyone who took the time to respond to my 
postings.

Tom Baker

-- 
Tom Baker - tbaker AT tbaker DOT de - baker AT sub DOT uni-goettingen DOT de

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