I think that what Juan means is that when you rsync from one system where
the archive bit is unset, to another place, these files, which were
archive=0 on their source, are new creations on the target system, and
have the archive bit set. Rsync has no provision to preserve these
attributes,
On 5 Dec 2001 at 15:02, Martin Pool wrote:
Date sent: Wed, 5 Dec 2001 15:02:34 +1100
From: Martin Pool [EMAIL PROTECTED]
To: Juan J. L?pez [EMAIL PROTECTED]
Copies to: [EMAIL PROTECTED]
Subject:Re: Netware modify bit
On Tue, Dec 04, 2001 at 12:51:07AM -0300, Juan wrote:
Hi,
I run rsync, with a Netware-directory mounted on a linux system
(using ncpfs) as DESTINATION of the copy. This configuration works fine,
but rsync incorrectly sets the archive bit (modify) for ALL the files
included in the
11:01:50 -0600
From: Dave Dykstra [EMAIL PROTECTED]
To: Juan [EMAIL PROTECTED]
Copies to: [EMAIL PROTECTED]
Subject:Re: Netware modify bit changed
On Tue, Dec 04, 2001 at 12:51:07AM -0300, Juan wrote:
Hi,
I run rsync
On 5 Dec 2001, Juan J. L?pez [EMAIL PROTECTED] wrote:
Dave:
With archive bit I mean a MS-DOS file attribute (like read
only, system or hidden). When the archive attribute of a
file is set, that file is presumed to be changed after the last
backup and then must be copied again. The
Hi,
I run rsync, with a Netware-directory mounted on a linux system (using ncpfs)
as
DESTINATION of the copy. This configuration works fine, but rsync incorrectly sets the
archive
bit (modify) for ALL the files included in the transfered directory (both modified and
not
modified).
