misc/164830: scp could not copy files
Gary Palmer
gpalmer at freebsd.org
Mon Feb 6 20:10:16 UTC 2012
The following reply was made to PR misc/164830; it has been noted by GNATS.
From: Gary Palmer <gpalmer at freebsd.org>
To: Eugen Konkov <kes-kes at yandex.ru>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: misc/164830: scp could not copy files
Date: Mon, 6 Feb 2012 15:08:54 -0500
On Mon, Feb 06, 2012 at 07:20:08PM +0000, Eugen Konkov wrote:
>
> >Number: 164830
> >Category: misc
> >Synopsis: scp could not copy files
> >Confidential: no
> >Severity: non-critical
> >Priority: low
> >Responsible: freebsd-bugs
> >State: open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class: sw-bug
> >Submitter-Id: current-users
> >Arrival-Date: Mon Feb 06 19:30:10 UTC 2012
> >Closed-Date:
> >Last-Modified:
> >Originator: Eugen Konkov
> >Release: 9-CURRENT
> >Organization:
> ISP FreeLine
> >Environment:
> >Description:
> I try to copy file from mail directory
> # ls -l 1328517293*
> -rw------- 1 vmail mail 14033 Feb 6 08:34 1328517293.M104652P74802.flux2,S=14033,W=14349:2,
>
> # scp '1328517293.M104652P74802.flux2,S=14033,W=14349:2,' adm at 10.1.1.1:/home/adm/in
> ssh: Could not resolve hostname 1328517293.M104652P74802.flux2,S=14033,W=14349: hostname nor servname provided, or not known
Your file name has a : in it. scp is treating the part before the colon
as a hostname. If you read scp(1) then you'll see:
File names may contain a user and host specification to indicate that the
file is to be copied to/from that host. Local file names can be made
explicit using absolute or relative pathnames to avoid scp treating file
names containing `:' as host specifiers. Copies between two remote hosts
are also permitted.
Try
scp './1328517293.M104652P74802.flux2,S=14033,W=14349:2,' adm at 10.1.1.1:/home/adm/in
More information about the freebsd-bugs
mailing list