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). In consecuence, the incremental backups on my netware server don't work. Any help will be apreciated. Regards, Juan J. Lopez
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 transfered directory (both modified and not modified). > In consecuence, the incremental backups on my netware server don't work.Do you mean the "access" time? If so, tell me what rsync command line you use because rsync normally will not change the access time of unmodified files. If you really mean "archive bit", it must be something in Netware that I've never heard of, and please explain what it is. - Dave Dykstra
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 backup aplication reset the "archive" attribute when copy a file. On the other hand, the operating system (DOS, Windows, etc) set it when the file is modified. Why rsync set this attribute on the copy, even when the original file is unchanged? Thanks, Juan On 4 Dec 2001 at 11:01, Dave Dykstra wrote: Date sent: Tue, 4 Dec 2001 11:01:50 -0600 From: Dave Dykstra <dwd@bell-labs.com> To: Juan <juan@comports.com> Copies to: rsync@lists.samba.org Subject: Re: Netware modify bit changed> 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 transfered directory (both modified and not modified). > > In consecuence, the incremental backups on my netware server don't work. > > Do you mean the "access" time? If so, tell me what rsync command line you > use because rsync normally will not change the access time of unmodified > files. If you really mean "archive bit", it must be something in > Netware that I've never heard of, and please explain what it is. > > - Dave Dykstra
On 5 Dec 2001, "Juan J. L?pez" <juan@comports.com> 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 backup aplication reset > the "archive" attribute when copy a file. On the other hand, the > operating system (DOS, Windows, etc) set it when the file is > modified. Why rsync set this attribute on the copy, even when the > original file is unchanged?So the desired behaviour is that rsync should make the archive bit have the same setting on the destination as on the source, or that it should always clear it? At the moment rsync is completely unaware of the A bit, so it will get the default OS behaviour which is probably to set the bit on newly modified files. If anybody who cares about this writes a reasonably clean patch to implement it then I guess it would be considered. I think Samba can optionally map the A bit to the Unix x bit. Perhaps you could try that. -- Martin
On 5 Dec 2001 at 15:02, Martin Pool wrote: Date sent: Wed, 5 Dec 2001 15:02:34 +1100 From: Martin Pool <mbp@samba.org> To: "Juan J. L?pez" <juan@comports.com> Copies to: rsync@samba.org Subject: Re: Netware modify bit changed> On 5 Dec 2001, "Juan J. L?pez" <juan@comports.com> 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 backup aplicationreset> > the "archive" attribute when copy a file. On the other hand, the > > operating system (DOS, Windows, etc) set it when the file is > > modified. Why rsync set this attribute on the copy, even when the > > original file is unchanged? > > So the desired behaviour is that rsync should make the archive bit > have the same setting on the destination as on the source, or that it > should always clear it? > > At the moment rsync is completely unaware of the A bit, so it will get > the default OS behaviour which is probably to set the bit on newly > modified files. > > If anybody who cares about this writes a reasonably clean patch to > implement it then I guess it would be considered. > > I think Samba can optionally map the A bit to the Unix x bit.Perhaps> you could try that. >
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, as there's really no unix attribute corresponding to the dos archive attribute. I'm guessing that system isn't preserved, either, and i wonder what the handling of read-only and hidden would be... is readonly equivalent to ugo-w, and is hidden ugo-r? The unix attribute for hidden is to start the filename with a dot. I would expect the dos attributes to just be ignored, and a readonly, system, hidden, readonly file from one system would arrive at another system as a non-system, readwrite, visible file, with the archive attribute set. Incidentally, since it's netware-to-netware, what about NCP? I don't know much about it, but i understand that it transfers the underlying netware information instead of going through all the filesystem layers... very fast, and i think it can go system-to-system within a netware domain. Does it still even exist post 3.12?> > On 5 Dec 2001, "Juan J. L?pez" <juan@comports.com> 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 backup aplicationTim Conway tim.conway@philips.com 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(nnnnnnnnnnnn, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' "There are some who call me.... Tim?"