Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	Andrew Markebo <andrew DOT markebo AT telia DOT com>
Subject:	Re: Peculiarities with tar
Date:	Mon, 14 Apr 2003 22:57:14 +0200
Lines:	37
Message-ID:	<m3vfxgssph.fsf@telia.com>
References:	<NGBBLLIAMFLGJEOAJCCEMEFJCOAA DOT garbage_collector AT telia DOT com>
Mime-Version:	1.0
X-Complaints-To:	usenet AT main DOT gmane DOT org
User-Agent:	Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.2 (gnu/linux)
Cancel-Lock:	sha1:PrRTGxVsbwumZ3mXDxeTq1UF8Gs=

/ "Hannu E K Nevalainen (garbage mail)" <garbage_collector AT telia DOT com> wrote:
| This might or might not be a cygwin/tar problem...
|
| It appears when tar is running, though...
|
|  Tonight I tried cygwin's tar for a simple backup, from a FAT32  partition,
| over a Windows SMB mount... The output ended up to be a seemingly functional
| archive, but with this in the console:
|
| --
| tar: Removing leading `//' from member names
| tar: //FUJITSU2/D/SPel/nfogrames/CivilizationIII/Civ3Edit.exe: file changed
| as we read it
| tar: //FUJITSU2/D/SPel/ACDSee32/UNWISE.EXE: file changed as we read it

[...]

|  //FUJITSU2/ is a 200MHz P2 and has McAfee 5.21 running on it.
| McAfee checks the files as they're read - does that affect tar's  behaviour?

I recognize this, saw similar problem, disappeared when disabling the
McAfee antivirus, give that a try.. 

How to get it fixed, turn off mcafee while backupping.

| - Is there a "last accessed date" on FAT32 partitions?
| - Does that change as McAfee reads files?
| - Shouldn't the fact that *tar* reads files also affect the date?

The data affected IMHO should only be raised when it is changed, not
read, problem could be that because fat32 don't have a read-tag, it is
mapped to changed.. and therefore the file gets 'updated' when read.

       /Andy

-- 
 The parser of the compiler rests on the code!


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -