You can use rsync with a pull:
rsync -a username@remote_host:/home/username/dir1 place_to_sync_on_local_machine
Alexandru roibu0771.781.689alexandru.ro...@live.com
> Date: Mon, 13 Jun 2016 22:26:28 +0100
> From: sean.b...@gmail.com
> To: centos@centos.org
> Subject: Re: [CentOS] scp
Hi,
This is fairly common. I would look into the use of a proxy command to do
exactly what you ask. In addition, though not strictly necessary, I also
would generally recommend rsync rather than scp*. Both of these are
documented on my page here:
On June 12, 2016 8:51:42 PM CEST, cpol...@surewest.net wrote:
>On 2016-06-12 19:07, H wrote:
>> On 06/12/2016 05:21 PM, J Martin Rushton wrote:
>> > -BEGIN PGP SIGNED MESSAGE-
>> > Hash: SHA1
>> >
>> > $ scp svr2:/path/to/source svr1:/path/to/dest
>> >
>> > You'll get twice the network
On June 12, 2016 4:05:59 PM EDT, Always Learning wrote:
>
>On Sun, 2016-06-12 at 20:43 +0200, H wrote:
>
>> There seems to be something broken when using scp between two remote
>> locations. Some posts on the 'net suggest using 'scp -3' to do an
>> intermediate copy to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/16 21:29, Jonathan Billings wrote:
>
>> On Jun 12, 2016, at 11:21 AM, J Martin Rushton
>> wrote:
>>
>> $ scp svr2:/path/to/source svr1:/path/to/dest
>>
>> You'll get twice the network traffic since the
On Jun 12, 2016, at 2:43 PM, H wrote:
> There seems to be something broken when using scp between two remote
> locations. Some posts on the 'net suggest using 'scp -3' to do an
> intermediate copy to the workstation between the two remote servers but that
> option does
> On Jun 12, 2016, at 11:21 AM, J Martin Rushton
> wrote:
>
> $ scp svr2:/path/to/source svr1:/path/to/dest
>
> You'll get twice the network traffic since the copy is running on your
> workstattoin (or whatever).
You probably meant:
$ scp -3
On Sun, 2016-06-12 at 20:43 +0200, H wrote:
> There seems to be something broken when using scp between two remote
> locations. Some posts on the 'net suggest using 'scp -3' to do an
> intermediate copy to the workstation between the two remote servers
> but that option does not seem to have
On 2016-06-12 19:07, H wrote:
> On 06/12/2016 05:21 PM, J Martin Rushton wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > $ scp svr2:/path/to/source svr1:/path/to/dest
> >
> > You'll get twice the network traffic since the copy is running on your
> > workstattoin (or
On 06/12/2016 08:28 PM, J Martin Rushton wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/16 18:07, H wrote:
On 06/12/2016 05:21 PM, J Martin Rushton wrote: $ scp
svr2:/path/to/source svr1:/path/to/dest
You'll get twice the network traffic since the copy is running on
your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/16 18:07, H wrote:
> On 06/12/2016 05:21 PM, J Martin Rushton wrote: $ scp
> svr2:/path/to/source svr1:/path/to/dest
>
> You'll get twice the network traffic since the copy is running on
> your workstation (or whatever).
>
> On 12/06/16
On 06/12/2016 05:21 PM, J Martin Rushton wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
$ scp svr2:/path/to/source svr1:/path/to/dest
You'll get twice the network traffic since the copy is running on your
workstattoin (or whatever).
On 12/06/16 15:40, H wrote:
I normally use ssh to log
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
$ scp svr2:/path/to/source svr1:/path/to/dest
You'll get twice the network traffic since the copy is running on your
workstattoin (or whatever).
On 12/06/16 15:40, H wrote:
> I normally use ssh to log into a remote server, change directory
> and
I normally use ssh to log into a remote server, change directory and then use
scp from there to copy files from another remote server to the first one.
Now the first server has been hit by continuous error correction messages from the ECC
controller, all of which are corrected, and I am unable
14 matches
Mail list logo