Hmm. It seems trying to put more than one pattern into the source
filespec confuses things.
I simplified it to only the sets:
scp -T -v -p buildhost:"/path/to/sets/@([bem]|tex)*" .
and that worked.
I changed the order around to get all the bits in one source filespec:
scp -T -v -p
On Fri, 1 Nov 2019 08:30:24 - (UTC), mlel...@serpens.de (Michael
van Elst) wrote:
> jdbaker%consolidated.net@localhost ("John D. Baker") writes:
>
> >On the remote, it invokes 'scp' with an undocumented "-f" (lowercase
> >"f") switch:
>
> > debug1: Sending command: scp -v -p -f
> >
jdba...@consolidated.net ("John D. Baker") writes:
>On the remote, it invokes 'scp' with an undocumented "-f" (lowercase
>"f") switch:
> debug1: Sending command: scp -v -p -f
> /path/to/@(sets/@([bem*|text.tgz)|kernel/netbsd-CUSTOM.gz)
>passing it the path/fileglob given on the local host.
On Thu, 31 Oct 2019, John D. Baker wrote:
> I added the "-T" switch (disable strict filename checking) and that made
> it work.
>
> I'll need to check, but as I use 'ksh' as login shell it would be nice
> if ksh/bash filename-generation [ !(), @(), etc. ] could be used. Maybe
> it's only
On Wed, 30 Oct 2019, John D. Baker wrote:
> used a command line like:
>
> $ scp -p buildhost:"/path/to/sets/[bem]* /path/to/sets/text.tgz
> /path/to/kernel/netbsd-CUSTOM.gz" .
>
> to copy relevant sets and kernel to the machine's local disk.
>
> Today when I tried my usual procedure to
On Thu, 31 Oct 2019 16:46:47 - (UTC), mlel...@serpens.de (Michael
van Elst) wrote:
> jdbaker%consolidated.net@localhost ("John D. Baker") writes:
>
> > $ scp -p buildhost:'/path/to/{sets/text.tgz,kernel/netbsd-CUSTOM.gz}' .
>
> >It prompted for the password and then I got:
>
> > scp:
jdba...@consolidated.net ("John D. Baker") writes:
> $ scp -p buildhost:'/path/to/{sets/text.tgz,kernel/netbsd-CUSTOM.gz}' .
>It prompted for the password and then I got:
> scp: /path/to/{sets/text.tgz,kernel/netbsd-CUSTOM.gz}: No such file or
> directory
% scp fud:'raid{0,1}.label' .
(For some reason, your recent messages have not reached me at all, not
even quarantined on my ISP's web-mail system.)
On Thu, 31 Oct 2019 17:14:46 +1100, matthew green
wrote:
> this is odd. probably some recent change is trying to protect you..
>
> can you try eg:
>
>scp
this is odd. probably some recent change is trying to protect you..
can you try eg:
scp buildhost:'{file1,file2}' .
to copy multiple files? ie, use shell globbing with a single word
vs multiple words..
.mrg.
On Wed, 30 Oct 2019, John D. Baker wrote:
> One machine can't use this due to network load, but in the past, I
> used a command line like:
>
> $ scp -p buildhost:"/path/to/sets/[bem]* /path/to/sets/text.tgz
> /path/to/kernel/netbsd-CUSTOM.gz" .
A single path with glob characters:
$ scp -p
On Wed, 30 Oct 2019, John D. Baker wrote:
> The build host was running up-to-date netbsd-9/amd64. The machine being
> updated was running netbsd-9/i386 from 16 October.
I used SSH and a tar pipeline to get the files and the host in question
is now running up-to-date netbsd-9/i386.
The scp
Usually, I use the "net" amd map to make my build hosts' RELEASE
directory available to machines for in-place updates.
One machine can't use this due to network load, but in the past, I
used a command line like:
$ scp -p buildhost:"/path/to/sets/[bem]* /path/to/sets/text.tgz
12 matches
Mail list logo
