Can the syncoid SSH port be specified on the command line?

[ewwhite]

A customer uses SSH port 2223 for the source server I'll be replicating from in syncoid. I have entries in /etc/ssh/ssh_config for the hostname to force port 2223:

Host *ancaste*
    Port 2223

I don't think syncoid honors this, so I'm looking for the cleanest way to be able to modify the SSH port on the fly without hardcoding the script.

[pferland]

Looking at the code for the syncoid script, on line 40, it has a check to see if $args{'sshport'} is set. So I am getting if you do -sshport=2223 it would take it.

[jimsalterjrs]

This is correct; sshport was a recently merged pull. It works as described.

---

Sent from my phone - please forgive any autocorrect / swipe errors.

On September 26, 2016 7:31:59 AM Phillip Ferland notifications@github.com
wrote:

Looking at the code for the syncoid script, on line 40, it has a check to
see if $args{'sshport'} is set. So I am getting if you do -sshport=2223 it
would take it.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#51 (comment)

[jimsalterjrs]

Syncoid should honor nearly anything set in ssh_config, including port
numbers, actually.

---

Sent from my phone - please forgive any autocorrect / swipe errors.

On September 26, 2016 7:21:03 AM Edmund White notifications@github.com wrote:

A customer uses SSH port 2223 for the source server I'll be replicating
from in syncoid. I have entries in /etc/ssh/ssh_config for the hostname to
force port 2223:

Host *ancaste*
    Port 2223

I don't think synced honors this, so I'm looking for the cleanest way to be
able to modify the SSH port on the fly without hardcoding the script.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#51

[ewwhite]

Yes, the -sshport=2223 works for me. Thank you.