From: Michael Albinus <michael.albinus@gmx.de>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: help-gnu-emacs@gnu.org, Tassilo Horn <tsdh@gnu.org>
Subject: Re: Dired command on same host
Date: Wed, 05 Jan 2022 15:37:04 +0100 [thread overview]
Message-ID: <87mtka5jvz.fsf@gmx.de> (raw)
In-Reply-To: <87lezu5o9a.fsf@elite.giraud> (Manuel Giraud's message of "Wed, 05 Jan 2022 14:02:41 +0100")
Manuel Giraud <manuel@ledu-giraud.fr> writes:
Hi Manuel,
>> I've just applied some tests. If I run "scp hostA:/path/to/file
>> hostB:/another/path", scp assumes the "-3" argument by default. That
>> means, it copies the file first from hostA to my local host, and copies
>> then from my local host to hostB - like Tramp does. The difference is,
>> that it keeps the local transfer file in /tmp.
>
> I've made the same test : scp hostA:/path/to/file hostB:/another/path
> and with a relatively large file (1.5 GB) and it works as expected
> without filling /tmp. I'm using scp on fairly recent openbsd machine.
>
> OTOH, the out-of-band method of tramp fills up my /tmp (which is only
> 256 MB). So maybe, having tramp out-of-band trying to "scp hostA:old
> hostB:new" before relying on other method could be enough without going
> to the trouble of out-of-band from hostA to hostB directly?
Likely, you're using an older scp version. This behavior has changed in
OpenSSH 8.7, see <https://www.openssh.com/txt/release-8.7>:
--8<---------------cut here---------------start------------->8---
* scp(1): this release changes the behaviour of remote to remote
copies (e.g. "scp host-a:/path host-b:") to transfer through the
local host by default. This was previously available via the -3
flag. This mode avoids the need to expose credentials on the
origin hop, avoids triplicate interpretation of filenames by the
shell (by the local system, the copy origin and the destination)
and, in conjunction with the SFTP support for scp(1) mentioned
below, allows use of all authentication methods to the remote
hosts (previously, only non-interactive methods could be used).
A -R flag has been added to select the old behaviour.
--8<---------------cut here---------------end--------------->8---
So Tramp needs even more checks in order to detect what scp supports.
Best regards, Michael.
next prev parent reply other threads:[~2022-01-05 14:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 10:24 Dired command on same host Manuel Giraud
2022-01-04 12:56 ` Michael Albinus
2022-01-04 16:25 ` Manuel Giraud
2022-01-04 18:33 ` Michael Albinus
2022-01-04 19:35 ` Tassilo Horn
2022-01-05 9:35 ` Manuel Giraud
2022-01-05 21:07 ` Tomas Hlavaty
2022-01-06 11:01 ` Michael Albinus
2022-01-07 15:50 ` Michael Albinus
2022-01-10 9:33 ` Manuel Giraud
2022-01-10 12:56 ` Michael Albinus
2022-01-10 14:07 ` Manuel Giraud
2022-01-10 15:00 ` Michael Albinus
2022-01-10 16:16 ` Manuel Giraud
2022-01-11 8:25 ` Michael Albinus
2022-01-11 8:59 ` Manuel Giraud
2022-01-11 9:10 ` Michael Albinus
2022-01-10 17:21 ` Yuri Khan
2022-01-11 8:29 ` Michael Albinus
2022-01-05 10:34 ` Michael Albinus
2022-01-05 13:02 ` Manuel Giraud
2022-01-05 14:37 ` Michael Albinus [this message]
2022-01-05 18:23 ` Manuel Giraud
2022-01-05 9:44 ` Manuel Giraud
2022-01-05 10:40 ` Michael Albinus
2022-01-05 11:08 ` Yuri Khan
2022-01-05 11:46 ` Michael Albinus
2022-01-05 19:55 ` Tassilo Horn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtka5jvz.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=tsdh@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).