<br><br><div><span class="gmail_quote">On 5/22/06, <b class="gmail_sendername">Paul V. Gratz</b> <<a href="mailto:pgratz@gratz1.com">pgratz@gratz1.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Monday 22 May 2006 10:25 am, Cole Tuininga wrote:<br>> On 5/22/06, Dylan Semler <<a href="mailto:dylan.semler@gmail.com">dylan.semler@gmail.com</a>> wrote:<br>> > I'm working remotely and I would like to record and transfer some NHL games
<br>> > while I'm away. I can use scp, but the internet connection here is less<br>> > than reliable and if the transfer gets inturrupted, I'm left with part of<br>> > the game and I have to start the transfer over. Is there any way to use scp
<br>> > or possible something else and resume a file transfer where it left off<br>> > whenever there's a break in the connection?<br>><br>> How about rsync? That can resume a partial transfer...<br>>
<br><br>You can also setup rsync to use ssh (scp) underneath, so this is<br>probably a good solution.<br>Paul</blockquote><div><br><br>Thanks, I'm using rsync now and it's working well. It also seems to be a bit faster than scp, so that's cool.
<br>Why is it so important to use ssh underneath? Can I verify that passing -e ssh to the rsync command is sufficient to tunnel it through ssh?<br><br>Dylan<br></div><br></div>