For the same filename, sometimes you have to specify a different filename to scp, depending on whether the file is on remote system or local one.
I have created a remote file whose filename "a b" is 3 chars long - ASCII codes 97, 32, 98 scp '[EMAIL PROTECTED]:a b' . doesn't work - prints: scp: a: No such file or directory scp: b: No such file or directory I have to type scp '[EMAIL PROTECTED]:a\ b' . which propagates to the scp process as a single argument containing a backslash, as can be seen with touch a\ b (creates a file named "a b") scp a\ b d - works scp 'a\ b' d - cp: a\ b: No such file or directory The manual page says I should specify "file1" and "file2", which (lacking further details) implies the filename is supplied without any further encoding. All the more without an encoding which depends on where the file actually lies. Sounds like a bug to me - the escaping for the remote shell is not being done correctly? Is this the intended behaviour of scp from OpenBSD 4.0? I would tell the version of the scp but scp -version, --version, -V and -v doesn't work and man scp doesn't contain the word "version". CL<
