On 09/10/15, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote: ---------------- Quoted text ------------------------
Try this: rsync -ah --stats 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ --------------------- End Quote ----------------------------------
Sorry, I was too fast, not paying attention, you want this I believe:
rsync -ah --stats root@192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/
That will use the default port on the remote host, you can override that without specifying the -e if required using -p <port>.
Ah, I should have checked your second email!
On 09/10/2015 02:31 PM, C Linus Hicks wrote:
On 09/10/15, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote: ---------------- Quoted text ------------------------
Try this: rsync -ah --stats 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ --------------------- End Quote ----------------------------------
Sorry, I was too fast, not paying attention, you want this I believe:
rsync -ah --stats root@192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/
That will use the default port on the remote host, you can override that without specifying the -e if required using -p <port>. _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 09/10/2015 02:31 PM, C Linus Hicks wrote:
On 09/10/15, C Linus Hicks wrote:
On 09/10/15, Robert Moskowitz wrote: ---------------- Quoted text ------------------------
Try this: rsync -ah --stats 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ --------------------- End Quote ----------------------------------
Sorry, I was too fast, not paying attention, you want this I believe:
rsync -ah --stats root@192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/
That will use the default port on the remote host, you can override that without specifying the -e if required using -p <port>.
$ rsync -ah --stats --delete -p 613 root@192.168.129.2:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp Unexpected remote arg: root@192.168.129.2:/etc/dhcp/ rsync error: syntax or usage error (code 1) at main.c(1330) [sender=3.1.1]
So not there yet. :(
On Thu, 10 Sep 2015 22:50:47 -0400 Robert Moskowitz wrote:
That will use the default port on the remote host, you can override that without specifying the -e if required using -p <port>.
$ rsync -ah --stats --delete -p 613 root@192.168.129.2:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp Unexpected remote arg: root@192.168.129.2:/etc/dhcp/ rsync error: syntax or usage error (code 1) at main.c(1330) [sender=3.1.1]
So not there yet. :(
From 'man rsync':
-p, --perms This option causes the receiving rsync to set the destination permissions to be the same as the source per- missions.
Try this:
rsync -ah --stats --delete root@192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp
On 09/10/2015 11:19 PM, Carl E. Hartung wrote:
On Thu, 10 Sep 2015 22:50:47 -0400 Robert Moskowitz wrote:
That will use the default port on the remote host, you can override that without specifying the -e if required using -p <port>.
$ rsync -ah --stats --delete -p 613 root@192.168.129.2:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp Unexpected remote arg: root@192.168.129.2:/etc/dhcp/ rsync error: syntax or usage error (code 1) at main.c(1330) [sender=3.1.1]
So not there yet. :( From 'man rsync':
-p, --perms This option causes the receiving rsync to set the destination permissions to be the same as the source per- missions.
Try this:
rsync -ah --stats --delete root@192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp
SSh is not parsing the port the way http does, it seems:
$ rsync -ah --stats root@192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp ssh: connect to host 192.168.129.2 port 22: No route to host rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
The reason why I change my SSH port is a simple way to keep port knocker robots away. Different hosts use different ports...
Am 11.09.2015 um 05:49 schrieb Robert Moskowitz rgm@htt-consult.com:
On 09/10/2015 11:19 PM, Carl E. Hartung wrote:
On Thu, 10 Sep 2015 22:50:47 -0400 Robert Moskowitz wrote:
$ rsync -ah --stats --delete -p 613 root@192.168.129.2:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp Unexpected remote arg: root@192.168.129.2:/etc/dhcp/ rsync error: syntax or usage error (code 1) at main.c(1330) [sender=3.1.1]
So not there yet. :( From 'man rsync':
-p, --perms This option causes the receiving rsync to set the destination permissions to be the same as the source per- missions.
Try this:
rsync -ah --stats --delete root@192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp
SSh is not parsing the port the way http does, it seems:
$ rsync -ah --stats root@192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp ssh: connect to host 192.168.129.2 port 22: No route to host rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
The reason why I change my SSH port is a simple way to keep port knocker robots away. Different hosts use different ports...
rsync -e 'ssh -p 613' -ah ...
-- LF
-
C Linus Hicks -
Carl E. Hartung -
Leon Fauster -
Robert Moskowitz