Re: why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-20 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK then... Because it would break an officially supported use case (rsh). It would also break the lsh utility included with rsync (in the support dir). The --rsh parameter is for specifying alternative remote shells that are command line compatible

why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-19 Thread Cameron Simpson
Why does rsync believe it knows more about the use of the token to the left of the colon than the program which will be used as the remote connection? I have a script called sshto with accepts targets like this: host1!host2!host3 and constructs the requisite ssh ProxyCommand options to do a

Re: why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-19 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Because it is an even bigger joy to be able to type 'ssh newhost' and have it just work even though you can't talk to newhost. You can do that by properly configuring ssh in ~/.ssh/config with something like this: Host accessiblehost User cameron

Re: why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-19 Thread Cameron Simpson
On 19Oct2011 12:02, Benjamin R. Haskell rs...@benizi.com wrote: | On Wed, 19 Oct 2011, Kevin Korb wrote: | Because it is an even bigger joy to be able to type 'ssh newhost' | and have it just work even though you can't talk to newhost. You | can do that by properly configuring ssh in

Re: why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-19 Thread Brian K. White
On 10/19/2011 6:58 PM, Cameron Simpson wrote: On 19Oct2011 12:02, Benjamin R. Haskellrs...@benizi.com wrote: | On Wed, 19 Oct 2011, Kevin Korb wrote: |Because it is an even bigger joy to be able to type 'ssh newhost' |and have it just work even though you can't talk to newhost. You |can do

Re: why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-19 Thread Cameron Simpson
On 19Oct2011 22:14, Brian K. White br...@aljex.com wrote: | On 10/19/2011 6:58 PM, Cameron Simpson wrote: | On 19Oct2011 12:02, Benjamin R. Haskellrs...@benizi.com wrote: | | rsync has to parse the URL you're passing. The fact that it then | | takes that and runs something like `$RSYNC_RSH -l

Re: why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-19 Thread Benjamin R. Haskell
On Thu, 20 Oct 2011, Cameron Simpson wrote: On 19Oct2011 12:02, Benjamin R. Haskell rs...@benizi.com wrote: | On Wed, 19 Oct 2011, Kevin Korb wrote: | Because it is an even bigger joy to be able to type 'ssh newhost' | and have it just work even though you can't talk to newhost. You | can do

Re: why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-19 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/19/11 18:58, Cameron Simpson wrote: On 19Oct2011 12:02, Benjamin R. Haskell rs...@benizi.com wrote: | On Wed, 19 Oct 2011, Kevin Korb wrote: | Because it is an even bigger joy to be able to type 'ssh newhost' | and have it just work even

Re: why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-19 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I should also point out that I am not making up cool distinctive names for my config file. I am using that actual host name of the system that I am trying to connect to so that I can type 'ssh hostname' as if I were plugged into the LAN that it was

Re: why does rsync translate user@host into '$RSYNC_RSH -l user host'?

2011-10-19 Thread Brian K. White
On 10/19/2011 11:38 PM, Cameron Simpson wrote: On 19Oct2011 22:14, Brian K. Whitebr...@aljex.com wrote: | On 10/19/2011 6:58 PM, Cameron Simpson wrote: |On 19Oct2011 12:02, Benjamin R. Haskellrs...@benizi.com wrote: || rsync has to parse the URL you're passing. The fact that it then || takes