Does anyone know how to specify a ssh port number with fanout?

I tried
hostnameort
hostname -p#
hostname -p #

and none worked.

should be
ssh user@hostname -p <port number>

Just tried it and it works for me.

Was that with fanout or fanterm?

No that was with the command line but doesn't fanout just initiate multiple commands?

Some what, the syntax is:
but you can't do server100 -p9999, nor server100:9999

According to a site that I found you can't do that. the syntax is
fanout [--noping] "{space separated list of systems}" "{commands to run}"

However this looks like it might help us a little.

A "System" is a bit of a misnomer; it could be a fully qualified domain, an entry in /etc/hosts, an IP address, an entry in ~/.ssh/config, or any of those preceeded with user_account@ . In short, if you can type ssh something and get a command prompt, it can be used as a "system" above.

so you might try to add the host to the ssh file and then call it.

Thanks!

This file?
so put the host and port number in there?

possibly. Here is some more information that I dug up.

Here is an example ~/.ssh/config file.

Host *panix.com
User suominen
Compression no

Host *gw.com
FallBackToRsh no

Host *
Compression yes
CompressionLevel 9
FallBackToRsh yes
KeepAlive no


however I can't find all the allowed attributes. I did just find this one from Red Hat magazine.

Host wiki.pretendco.com
Hostname localhost
Port 2200

Thanks I'll check that out.

I think this will help you out a lot.

http://magazine.redhat.com/2007/11/27/advanced-ssh-configuration-and-tunneling-we-dont-need-no-stinking-vpn-software/

Actually the fanout binary is actually a script not a binary, so I can just add -p9999 to the source code to the fanout script.

Or if you have multiple ports you use you can just make multiple copies of fanout.

Ex: fanout8 for port 8765
fanout9 for 9999
etc.

nice so it looks like you have two ways to accomplish that. If you create the config file then you only have to maintain one copy of it. However if that doesn't work then as you said you can create multiple fanout files.

Too many tools that run "ssh" to communicate with a remote host are not considering the port number as one of the elements of identifying the remote. I don't know about "fanout" but I know I have this trouble with "rsync". Part of the problem is "ssh" didn't really integrate the port number as part of the remote identity, probably due to the history of "ssh" using separate options. If you will note, the URL does have a capability to include a port number.

I get around this by front-ending "ssh" with a script first in my path called "ssh". This is found by "rsync" as expected. My script checks for an explicit "-p" option and uses that if present. Else it checks for an environment variable "SSHPORT" and uses that for the path. Else it does a lookup via an alternate configuration data tree based on both username and hostname. Else it just runs "ssh" without a "-p" option and lets "ssh" figure it out based on its usual limited config file.

But it really would have helped if we had a better "login resource locator" that included the port number along with the username and hostname (or IP address).