(no subject)

[Tim Conway]

Run it this way:
/usr/local/bin/rsync -aHnuvvv serverX:/ / --exclude-from=/rsync.exclude 
--rsync-path=/usr/local/bin/rsync --ignore-existing 2>&1 |tee 
/tmp/rsync.debug

The extra verbosity will show you what transport you're using, and other 
problems.  It could be that you're sshing in, and the authorized_keys file 
on serverX has command restrictions, for instance, so it just throws you 
out as soon as rsync invokes the remote.  Combining stdout and stderr lets 
you see how they fit together.  tee just lets you watch as it goes.
Good luck.

Tim Conway
Unix System Administration
Contractor - IBM Global Services
desk:3032734776
conway at us.ibm.com


>From the local machine the following command is executed:
 
/usr/local/bin/rsync -aHnuv serverX:/ / --exclude-from=/rsync.exclude 
--rsync-path=/usr/local/bin/rsync --ignore-existing > 
/var/tmp/rsync.stdout 2> /var/tmp/rsync.stderr
 
I have never used the rsync command. The above command was used by a 
former sysadmin to "synchronize" two servers. However when I ran the 
command it did not produce any "dry -run" output ("n" option). A check of 
the /var/tmp/rsync.stderr shows the following output ws produced: "rsync: 
connection unexpectedly closed (0 bytes read so far); rsync error: error 
in rsync protocl data stream (code 12) at io.c(165)."
 
Based on the above syntax, what was included/excluded that made this not 
work, and what is the correct syntax to "sync" the local machine to the 
remote?
In advance, thanks for the help.