rsync - May 2010 - The source and destination cannot both be remote :-(

Moin,

this is something for the wish list: a 'rsync in the middle' mode. It
would make sense: rsync is running at a server. Copyying files from one
maschine to a file server.
rsync root at client:/var/tmp/in tomcat at fileserver:/opt/

Would this be possible without breaking the hard link mechanism?

CU
-- 
|Michael Renner      E-mail: michael.renner at gmx.de  |
|D-81541 Munich      Germany        ICQ: #112280325 |
|Germany             Don't drink as root!      ESC:wq

7 maj 2010 kl. 17.43 skrev Michael Renner:
> Moin,
>
> this is something for the wish list: a 'rsync in the middle' mode.
It
> would make sense: rsync is running at a server. Copyying files from  
> one
> maschine to a file server.
> rsync root at client:/var/tmp/in tomcat at fileserver:/opt/
>
> Would this be possible without breaking the hard link mechanism?
That I have no idea about, but I believe it would double the bandwith  
requirements or half the speed compared to

ssh root at client "rsync /var/tmp/in tomcat at fileserver:/opt/"

It would however be quite useful in some situations...

Christian Huldt wrote:
> That I have no idea about, but I believe it would double the bandwith  
> requirements or half the speed compared to
> 
> ssh root at client "rsync /var/tmp/in tomcat at fileserver:/opt/"
It would likely increase the latency, but it should not significantly
impact the required bandwidth, assuming that you have a full-duplex
connection. If you have a half-duplex connection, yes, the bandwidth
consumption would double.

--Kyle

7 maj 2010 kl. 21.20 skrev Kyle Lanclos:
>
> It would likely increase the latency, but it should not significantly
> impact the required bandwidth, assuming that you have a full-duplex
> connection. If you have a half-duplex connection, yes, the bandwidth
> consumption would double.
I stand corrected and further educated. (And I really should get a  
better connection...)

Great list!

Christian