On Thu, 4 Aug 2005, Keith Warno wrote:
> Thanks for the replies. All the proposed solutions should've been
> obvious to me. :/ Is it Friday yet...? nope... dang...
>
> Yes I like the config file method as well, so long as I remember to use
> the same local port # when establishing the tunnel.
Thanks for the replies. All the proposed solutions should've been
obvious to me. :/ Is it Friday yet...? nope... dang...
Yes I like the config file method as well, so long as I remember to use
the same local port # when establishing the tunnel.
keith
--
SA Valaran Corp
GPG: 0xEC705AE9
I put th
On Thu, Aug 04, 2005 at 02:33:28PM -0400, Keith Warno wrote:
> is there a way to pass an SSH port # to rsync?
I agree with Jos that the best way is to use your .ssh/config file
(assuming you don't need multiple ports per hostname). Otherwise,
use the -rsh (-e) option to rsync:
-e 'ssh
On Thu 04 Aug 2005, Keith Warno wrote:
> Perhaps this is a lame question, but...
>
> is there a way to pass an SSH port # to rsync?
rsync -e 'ssh -p 12345' ...
I usually do this in the form 'ssh -c arcfour' as that cipher uses far
less cpu power than the default.
Paul Slootman
--
To un
On Thu, Aug 04, 2005 at 02:33:28PM -0400, Keith Warno wrote:
> Perhaps this is a lame question, but...
>
> is there a way to pass an SSH port # to rsync?
>
> At least one way I can do it is to use a small shell wrapper around ssh
> and pass the port # thru the environment. Just wondering i
Perhaps this is a lame question, but...
is there a way to pass an SSH port # to rsync?
At least one way I can do it is to use a small shell wrapper around ssh
and pass the port # thru the environment. Just wondering if there is an
easier way that I magically can't find.
The reason for t
