From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: syntax problems with scp/rsync
Date: Mon, 11 Sep 2006 23:58:25 -0700 [thread overview]
Message-ID: <45065A91.5000803@comarre.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0609111110430.23966-100000@treebeard.engin.umich.edu>
Karthik Vishwanath wrote:
> Hello,
>
> I seem to be having some difficulty using scp and rsync with the most
> basic commands giving me problems:
>
> $ scp kvh1@godzilla.acpub.duke.edu:FN* .
> usage: scp [-1246BCpqrv] [-c cipher] [-F ssh_config] [-i identity_file]
> [-l limit] [-o ssh_option] [-P port] [-S program]
> [[user@]host1:]file1 [...] [[user@]host2:]file2
>
> $ rsync kvh1@godzilla.acpub.duke.edu:FN* .
> rsync version 2.6.6 protocol version 29
> ...
> rsync error: syntax or usage error (code 1) at main.c(897)
>
> However, both commands (listed below) work fine:
> $ scp t* kvh1@godzilla.acpub.duke.edu:
> $ rsync t* kvh1@godzilla.acpub.duke.edu:
>
>
> What is going on to cause the incorrect syntax in attempting to retrieve
> files from the remote host?
I don't use rsync here so focused on scp.
After verifying that I could use similar syntax here on my LAN with no
errors, I went ahead and tried what you have above:
autovcr@firefly:~$ scp kvh1@godzilla.acpub.duke.edu:FN* .
The authenticity of host 'godzilla.acpub.duke.edu (152.3.233.25)' can't
be established.
RSA key fingerprint is 04:53:67:16:20:e4:61:88:61:a8:25:f0:ff:54:7a:73.
Are you sure you want to continue connecting (yes/no)? no
Host key verification failed.
In other words, it worked fine for me. That's using OpenSSH 1:4.3p2-3
from Debian-Sid, from bash on a vt.
So I'd suspect one of three things:
1. a non-printing character in the command string. Likely only if you
didn't actually retype the "kvh1@godzilla.acpub.duke.edu:FN* ." part
between the two tries.
2. a problem with your shell.
3. You are using a non-standard ssh/scp program. Unlikely, since the
error response matches exactly.
Some programs fail if wildcards expand ambiguously in the pwd (find is
notorious for that, as an example), but I tested that here and scp
doesn't do that.
Sorry I can't offer more help.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2006-09-12 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 15:21 syntax problems with scp/rsync Karthik Vishwanath
2006-09-12 6:58 ` Ray Olszewski [this message]
2006-09-12 12:42 ` Karthik Vishwanath
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45065A91.5000803@comarre.com \
--to=ray@comarre.com \
--cc=linux-newbie@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.