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

[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 with rsh.

In this discussion we have 2 well known use cases plus a basic design
feature verses a single user's custom solution that could probably be
easily re-customized to be rsh command line compatible.

On 10/20/11 01:57, Brian K. White wrote:
> On 10/20/2011 12:08 AM, Kevin Korb wrote:
> 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 on.
> 
> I can sit at my house with my 172.22.100.0/24 private IP, type 'ssh
> hostname', and end up logged into a server at work with a
> 192.168.42.0/24 private IP.  I got there by actually connecting to a
> real internet IP address/host name but I don't have to specify that
> every stinking time I want to ssh.
> 
>> Some of us ssh from random machines to other random machines.
>> Some ssh servers and clients are on appliances that are either
>> impossible or completely impractical to configure ~/.ssh/* or don't even
>> have any such thing as ~/.ssh/* in fact openssh is not even the only ssh
>> server or client even when you are dealing with a unix-like system.
> 
>> Configuring ~/.ssh/* is nice in some cases, and utterly impractical, or
>> not even possible in others.
> 
>> The OP's question was not about other ways to use ssh but why rsync
>> couldn't allow the user to supply an unpredicted type of url that they
>> happen to know would work if rsync would just not try to parse it but
>> just collect it and and hand it off.
> 
> 
> On 10/19/11 23:58, Kevin Korb wrote:
>>>> you find it easier to make a bunch of ssh config clauses first, each
>>>> with cool distinctive names? I salute your typing skills.
> 

- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			http://www.sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6gE/4ACgkQVKC1jlbQAQeszgCgn7mWokNiLD9WMJlTxOrLdWoT
BOkAn2YfwA4cP8QejqVHizvtrDC3jDaX
=2ZXJ
-----END PGP SIGNATURE-----