Not quite a bash escaping problem, it’s scp treating x: as a [user@]host prefix, try: scp ./file:\ name.mp4 user@host:”/path/to/dest” Using relative (e.g. ./) or fully qualified paths (/path/to/source) prevents this behaviour – the presence of / before a : causes OpenSSH to stop checking for a possible host: or user@host: prefix). OpenSSH’s scp only special-cases … Read more
You may be looking for rsync -aR for example: rsync -a –relative /top/a/b/c/d remote:/ See also this trick in other question.
You need to tell scp where to send the file. In your command that is not working: scp C:\Users\Admin\Desktop\WMU\5260\A2.c ~ You have not mentioned a remote server. scp uses : to delimit the host and path, so it thinks you have asked it to download a file at the path \Users\Admin\Desktop\WMU\5260\A2.c from the host C … Read more
Make sure the scp command is available on both sides – both on the client and on the server. If this is Fedora or Red Hat Enterprise Linux and clones (CentOS), make sure this package is installed: yum -y install openssh-clients If you work with Debian or Ubuntu and clones, install this package: apt-get install … Read more
TLDR: use synchronize instead of copy. Here’s the copy command I’m using: – copy: src=testdata dest=/tmp/testdata/ As a guess, I assume the sync operations are slow. The files module documentation implies this too: The “copy” module recursively copy facility does not scale to lots (>hundreds) of files. For alternative, see synchronize module, which is a … Read more
I ended up using Jsch- it was pretty straightforward, and seemed to scale up pretty well (I was grabbing a few thousand files every few minutes).
There’s no way to initiate a file transfer back to/from local Windows from a SSH session opened in PuTTY window. Though PuTTY supports connection-sharing. While you still need to run a compatible file transfer client (pscp or psftp), no new login is required, it automatically (if enabled) makes use of an existing PuTTY session. To … Read more
Using echo in a .bashrc will break scp, as scp expects to see its protocol data over the stdin/stdout channels. See https://bugzilla.redhat.com/show_bug.cgi?id=20527 for more discussion on this issue. There’s a few workarounds available: Condition on the ‘interactive’ flag (e.g. case $- in *i* as suggested by tripleee) Use the tty utility to detect an interactive … Read more
I knew that it was possible, I just took wrong tool. I did it with rsync rsync –progress -avhe ssh /usr/local/ XXX.XXX.XXX.XXX:/BackUp/usr/local/