Mailinglist Archive: opensuse (3100 mails)

< Previous Next >
Re: [SLE] Using rsync
  • From: John D Lamb <J.D.Lamb@xxxxxxxxxxxxxx>
  • Date: Thu, 23 Mar 2006 07:54:33 +0000
  • Message-id: <44225439.2070105@xxxxxxxxxxxxxx>
Susemail wrote:
> I have a new computer 64bit, Suse 10.0 (dest ) and an old computer 32bit, Suse
> 10.0 (src) on my Lan. I have copied my home directory from the old to the
> new using rsync, but certain files like .bash_history did not transfer.
>
> Using the example in the manual: rsync -avz foo:src/bar /data/tmp on 'dest'
> like this:
> rsync -avz 192.168.0.8:home/myhome/z_rsync_test /home/myhome
> just hangs no error messages -- nothing.
>
> Whereas using it like this on 'src' works:
> rsync -avz /home/myhome/z_rsync_test 192.168.0.4:
>
rsync uses rsh or ssh to connect. If the remote machine is blocking
these then it won't work. Try finding out which rsync uses on your
machines and test by using rsh remote or ssh remote. Better still,
always use ssh (even on a private network it's now easier to get ssh
right): rsync -avz -e ssh ... and test ssh first.

> except that some files are not copied like .bash_history and my mail files
> seem to have been copied but the accounts in Kmail on the new machine have
> not been created.

Files beginninng with . perhaps? I can't remember whether rsync is
supposed to copy these by default but you should can change the
behaviour using the --include or --include-from options. I've had
problems with long lists if you use the first and so would recommend the
second. If you really want to copy these then the pattern is \.* But
beware: if you've carefully set up ssh on two mahines (for example to
avoid passwords) and overwrite the .ssh directory with rsync, you will
have problems. You might, for example, copy only some mail directories
and change folder names appropriately. I use a small bash script to
handle such things, copy Mozilla local folders, but let IMAP accounts
handle themselved.

> In the first example when I rsync using the format in the man page and it
> hangs, what am I doing wrong.
>
> In the second example why does rsync -avz /home/myhome/z_rsync_test
> 192.168.0.4: work
>
> while rsync -avz /home/myhome/z_rsync_test 192.168.0.4:home/adriel/ does not:
> Password:
> building file list ... done
> rsync: mkdir "/home/myhome/home/myhome" failed: No such file or directory (2)
> rsync error: error in file IO (code 11) at main.c(422)
> rsync: connection unexpectedly closed (8 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(434)
>
> I assume it is because in this instance my home directory is the 'root'
> directory since I'm logged in as my user. Is this true?

Probably: rsync logs in using ssh or rsh and has only the permissions of
the user it logs in as. You could try the user@host option. Usually it
is not a good idea to have user files on one machine become root files
on another.

--
JDL

< Previous Next >
This Thread
References