SSH on another port - Githubissues

antirek / lsyncd

Automatically exported from code.google.com/p/lsyncd

GNU General Public License v2.0

0 stars 1 forks source link

SSH on another port #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
My ssh server is not on port 22, how can I instruct lsyncd to use my other
port, I tried the xml config file with no luck.

What is the expected output? What do you see instead?
Fail

What version of the product are you using? On what operating system?
last release

Please provide any additional information below.

Thanks
Thomas

Original issue reported on code.google.com by mic...@gmail.com on 14 Aug 2009 at 3:28

GoogleCodeExporter commented 9 years ago

It works for me.
Add in the callopts section:

<option text="--rsh=ssh -p PortNumber"/>

bye

Original comment by tenyos...@gmail.com on 10 Mar 2010 at 12:26

GoogleCodeExporter commented 9 years ago

this works for one host, but what if you are syncing with multiple destination 
hosts, 
and all/some of them have different ports for SSH?

Original comment by phil.cryer on 19 May 2010 at 6:23

GoogleCodeExporter commented 9 years ago

You can specifiy call-opts as local parameters in every directory part.

Original comment by axk...@gmail.com on 11 Jul 2010 at 7:06

Changed state: Done

GoogleCodeExporter commented 9 years ago

Hey, did you get a solution for this? I'm also trying lsyncd and would need to 
have different ports for different servers.

Original comment by andrebr...@gmail.com on 16 Dec 2010 at 2:28

GoogleCodeExporter commented 9 years ago

andrebruce, which lsyncd version are you refering to?

Original comment by axk...@gmail.com on 17 Dec 2010 at 2:05