scp remote path specification

Frank Tobin ftobin at uiuc.edu
Wed Dec 20 12:43:28 EST 2000


Markus Friedl, at 10:51 +0100 on Tue, 19 Dec 2000, wrote:

    many people have already problems with
    	scp hosta:/file1 hostb:/file2
    expanding to
    	ssh hosta 'scp /file1 hostb:/file2'

True, openssh appears really broken when having multiple remote hosts on
the command line (e.g., it doesn't even appear to do proper name lookups
on the second host with "scp fqdn:/etc/hosts non-fqdn:hosts"; I haven't
figured out what the other problems are yet), but that doesn't mean we
should further cut off the possible of expanded functionality.  If it were
possible, it surely stands that some are going to want to do:

scp a:file1 b:file2 c:file3 d:file4 final_host:final_dir/

If you _ever_ want to do this sort of thing in the future, you need to at
least let your design account for it.  For example, let the remote-path
specification be put into the config file, where you can do host-specific
options, instead of an argument, where it is much more difficult to do so.

-- 
Frank Tobin		http://www.uiuc.edu/~ftobin/






More information about the openssh-unix-dev mailing list