Changes between Version 23 and Version 24 of MTO

Timestamp:

11/26/13 13:41:05 (11 years ago)

Author:

jorisborgdorff

Comment:

--

MTO

@@ -15 +15 @@
 
 Before running MTO, its configuration files must be set to connect all clusters that will be used in a simulation. MTOs configuration is stored in three files:
- * The global topology file (`$MUSCLE_HOME/etc/mto-topology.cfg`) that states what clusters will be connected by the MTO and on which port it will listen for connecting MTOs. The file should be the same for all participating MTOs.
+ * The global topology file (`$MUSCLE_HOME/etc/mto-topology.cfg`) states what clusters will be connected by the MTO and on which port it will listen for connecting MTOs. The file should be the same for all participating MTOs.
  {{{
 // Comment
 # Comment
 
-# host definiton
+# Host definition:
 # <name> <address> [<port>]
-# if port is ommited, this MTO will not listen for incomming connections
+# If the port is omitted, this MTO will not listen for incoming connections.
+# Having few listening hosts may cause a performance penalty; at least one host should listen for connections.
 
 A localhost
@@ -29 +30 @@
 D localhost 5300
  }}}
- * The local configuration file ( `$MUSCLE_HOME/etc/mto-config.cfg`) that states how the MTO can be contacted by MUSCLE 2 within the cluster. It also specifies a limited port range on a given cluster, which should be different for each participating cluster. The `internalAddress` may be set to an IP-address or hostname that is accessible from all nodes in the cluster. If the host has multiple internet interfaces, the wildcard address `*` may also be specified here. For example, the wildcard is useful for aliasing the hostnames `localhost` and the fully qualified domain name and for running the MTO in a virtual machine.
+ * The local configuration file (`$MUSCLE_HOME/etc/mto-config.cfg`) states how the MTO can be contacted by MUSCLE 2 within the cluster. It also specifies a limited port range on a given cluster, which should be different for each participating cluster. The `internalAddress` may be set to an IP-address or hostname that is accessible from all nodes in the cluster. If the host has multiple internet interfaces, the wildcard address `*` may also be specified here. For example, the wildcard is useful for aliasing the hostnames `localhost` and the fully qualified domain name and for running the MTO in a virtual machine.
  {{{
 # Name of this MTO as in mto-copology.cfg
@@ -45 +46 @@
 internalAddress = private-address
  }}}
- * The MUSCLE 2 configuration (`$MUSCLE_HOME/etc/muscle.defaults`) that makes the information about the local MTO available to MUSCLE 2. This should match the local `mto-config.cfg` file. 
+ * The MUSCLE 2 configuration (`$MUSCLE_HOME/etc/muscle.defaults`) makes the information about the local MTO available to MUSCLE 2. This should match the local `mto-config.cfg` file. 
  {{{
 # Make the MTO available to MUSCLE.