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: http://www2.physics.ox.ac.uk/it-services/central-ssh-access Its got an Oxford Physics specific slant to it but hopefully its helpful. *I don't think rsync has any issue when the remote machine prints things either. Sean On 13 Jun 2016 7:26 pm, "H" <agents at meddatainc.com> wrote: > On June 12, 2016 8:51:42 PM CEST, cpolish at 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 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 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 to get a command line to issue the required commands to > >> > > change directory and then run scp from the other server. I have > >no > >> > > problems, however, getting into the first server - except for > >being > >> > > drowned by the error correction messages and the server seems to > >be > >> > > running "fine". > >> > > > >> > > Until I am able to get to the server and investigate, is it > >> > > possible to accomplish the above on a single command line, thus > >> > > avoiding seeing the error messages? I should add that both the > >> > > first and second server are set up to accept keys and not > >passwords > >> > > so at least I don't have to worry about that. > > > >Try changing kernel console log level to 0, possibly: > > > > echo '0 0 0 0' > /proc/sys/kernel/printk > > > >should take effect instantly. You _might_ be able to do this > >remotely via ssh. Also possibly can do via magic sysrq + 0. > > > >(see: RHEL 6 Deployment Guide (rev 3.1 2011-05-19) Appendix C > >pp.537-538) > > > >HTH, HAND, > >-- > >Charles Polisher > > > >_______________________________________________ > >CentOS mailing list > >CentOS at centos.org > >https://lists.centos.org/mailman/listinfo/centos > > Tried it but did not work since I am not root... > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >