Re: rsync and backup
Re: rsync and backup
- Subject: Re: rsync and backup
- From: Gnarlodious <email@hidden>
- Date: Wed, 9 Aug 2006 09:34:38 -0600
rsync will always transfer all resource files, since they have no
modtime associated with them. Resource files are normally rather
small, so it may not be the source of your slowness. Using the
"--size-only" modifier works to not transfer resource files of the
same size, except that for certain kinds of applications this may not
be a good idea. Tex-Edit for example uses a resource file to store
styling information about a text file. You can edit the text file and
change its size but not the size of the resource file. This results in
a wacko Tex-Edit window on the target machine, so I don't recomment
size-only unless you are willing to lose resource forks. Ideally rsync
in the future will apply datafile modtimes to the resource file, even
though it sees an entirely separate file. We will have to wait and see
if that happens in Leopard (10.5).
As to SSH, yes, setting up passwordless connecting is very much worth
it. When you said rsync wanted a password that is because SSH is not
set up on your network. Be sure to enable "Remote Login" in the
Sharing Prefpanel to login using SSH. many useful UNIX commands use
SSH, not just rsync. The page you went to may not be a good tutorial,
it seems there are no concise instructions for setting up SSH for OSX.
It is something that needs to be done. SSH is very particular about
permission on the SSH files, that is a common pitfall for beginners.
SSH checks the permissions for all components of the entire path to
the SSH folder, if one component has too liberal permissions it will
fail without reporting the problem. The system, however, writes the
error to the logs.
Firewire is much faster that Wi-Fi. Personally I would not recommend
rsync over Wi-Fi unless you know files are a reasonable length. rsync
is surprisingly persistent in its transferring, refusing to quit as
long as there is a little bandwidth.
rsync is an evolving tool, in 10.3 resource forks were not even
supported. The fact that rsync, ot at least the OSX version, is now
handling resource files is a good sign. Of course, *NIX machines still
do not recognize resource forks, the file is stored and handled as an
ordinary file. rsync on Linux machines does not work if you send the
-E option. It is possibly future versions of rsync will include the
extended attributes option even for Linux and Windows.
-- Gnarlie
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden