-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At some point hitherto, Michael O'Donnell hath spake thusly:
> I can hack around this in a number of ways (like
> issuing two separate scp commands with the files
> temporarily residing on C's disk, or by spawning a
> tar on L and one on R and pushing the data from one to
> the other via two pipelined ssh's on C, etc, etc) but
> I wonder if there is some more elegant approach...?
If this is something you plan to do fairly often, I'd write a shell
script wrapper around scp called scpproxy that essentially did:
for file in $@; do
scp $file tmpfile
scp tmpfile destination
rm tmpfile
done
The processing would be a little more complicated than that, since
your destination would be the last command-line arg, and there could
be more than one source file in the scp command. I'm just in a hurry
to leave to write it... headed to the beach. ;-)
- --
Derek Martin [EMAIL PROTECTED]
- ---------------------------------------------
I prefer mail encrypted with PGP/GPG!
GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu
Learn more about it at http://www.gnupg.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9fjx+djdlQoHP510RAjirAJ9tX5l4N8PdhVe5dR/OaRgX3JnflwCfc1Kt
K2IQMdfnwlRFFVrmZ5TzhAM=
=/b7y
-----END PGP SIGNATURE-----
_______________________________________________
gnhlug-discuss mailing list
[EMAIL PROTECTED]
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
