On Mon, 11 Sep 2006, at 23:58, Ray Olszewski wrote to linux-newbie@xxxxxxxxxxx: > 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@xxxxxxxxxxxxxxxxxxxxxxx: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 > > [snip'd] > > 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@xxxxxxxxxxxxxxxxxxxxxxx: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. > The mystery is solved, thanks to your notes above, Ray -- it did involve wildcard expansions. The problem could be overcome by using: scp 'kvh1@xxxxxxxxxxxxxxxxxxxxxxx:FN*' . bash had the "nullglob" option set, once removed, the single quotes were not required. Thanks for the assistance. -K - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
