- value to 0. When set to 1, or missing from the environment, RMR will invoke the
- connection interface in the transport mechanism using the non-blocking (async)
- mode. This will likely result in many "soft failures" (retry) until the connection
- is established, but allows the application to continue unimpeeded should the
- connection be slow to set up.
- &half_space
-
-&ditem(RMR_BIND_IF) This provides the interface that RMR will bind listen ports to allowing
- for a single interface to be used rather than listening across all interfaces.
- This should be the IP address assigned to the interface that RMR should listen
- on, and if not defined RMR will listen on all interfaces.
- &half_space
-
-&ditem(RMR_CTL_PORT)
- This variable defines the port that RMR should open for communications
- with Route Manager, and other RMR control applications.
- If not defined, the port 4561 is assumed.
-
- &space
- Previously, the &cw(RMR_RTG_SVC) (route table generator service port)
- was used to define this port.
- However, a future version of Route Manager will require RMR to connect
- and request tables, thus that variable is now used to supply the Route
- Manager well known address and port.
-
- &space
- To maintain backwards compatablibility with the older Route Manager versions,
- the presence of this variable in the environment will shift RMR's behaviour
- with respect to the default value used when &cw(RMR_RTG_SVC) is &bold(not) defined.
-
- &space
- When &cw(RMR_CTL_PORT) is &bold(defined^:)
- RMR assumes that Route Manager requires RMR to connect and request table
- updates is made, and the default well known address for Route manager
- is used (routemgr:4561).
-
- &space
- When &cw(RMR_CTL_PORT) is &bold(undefined^:)
- RMR assumes that Route Manager will connect and push table updates, thus the
- default listen port (4561) is used.
-
- &space
- To avoid any possible misinterpretation and/or incorrect assumptions on the part
- of RMR, it is recommended that both the &cw(RMR_CTL_PORT) and &cw(RMR_RTG_SVC)
- be defined.
- In the case where both variables are defined, RMR will behave exactly as is
- communicated with the variable's values.
- &half_space
-
-&ditem(RMR_RTG_SVC)
- The value of this variable depends on the Route Manager in use.
- &space
- When the Route Manager is expecting to connect to an xAPP and push
- route tables, this variable must indicate the &cw(port) which RMR should
- use to listen for these connections.
-
- &space
- When the Route Manager is expecting RMR to connect and request a
- table update during initialisation, the variable should be the
- &cw(host:port) of the Route Manager process.
-
- &space
- The &cw(RMR_CTL_PORT) variable (added with the support of sending table update
- requests to Route manager), controls the behaviour if this variable is not set.
- See the description of that variable for details.
- &half_space
-
-&ditem(RMR_HR_LOG)
- By default RMR writes messages to standard error (incorrectly referred to as log messages)
- in human readable format.
- If this environment variable is set to 0, the format of standard error messages might
- be written in some format not easily read by humans.
- If missing, a value of 1 is assumed.
- &half_space
+ value to 0). When set to 1, or missing from the environment, RMR will invoke the
+ connection interface in the transport mechanism using the non-blocking (async)
+ mode. This will likely result in many "soft failures" (retry) until the connection
+ is established, but allows the application to continue unimpeded should the
+ connection be slow to set up.
+ &half_space
+
+&ditem(RMR_BIND_IF) This provides the interface that RMR will bind listen ports to, allowing
+ for a single interface to be used rather than listening across all interfaces.
+ This should be the IP address assigned to the interface that RMR should listen
+ on, and if not defined RMR will listen on all interfaces.
+ &half_space
+
+&ditem(RMR_CTL_PORT)
+ This variable defines the port that RMR should open for communications
+ with Route Manager, and other RMR control applications.
+ If not defined, the port 4561 is assumed.
+
+ &space
+ Previously, the &cw(RMR_RTG_SVC) (route table generator service port)
+ was used to define this port.
+ However, a future version of Route Manager will require RMR to connect
+ and request tables, thus that variable is now used to supply the Route
+ Manager's well-known address and port.
+
+ &space
+ To maintain backwards compatibility with the older Route Manager versions,
+ the presence of this variable in the environment will shift RMR's behaviour
+ with respect to the default value used when &cw(RMR_RTG_SVC) is &bold(not) defined.
+
+ &space
+ When &cw(RMR_CTL_PORT) is &bold(defined^:)
+ RMR assumes that Route Manager requires RMR to connect and request table
+ updates is made, and the default well-known address for Route manager
+ is used (routemgr:4561).
+
+ &space
+ When &cw(RMR_CTL_PORT) is &bold(undefined^:)
+ RMR assumes that Route Manager will connect and push table updates, thus the
+ default listen port (4561) is used.
+
+ &space
+ To avoid any possible misinterpretation and/or incorrect assumptions on the part
+ of RMR, it is recommended that both the &cw(RMR_CTL_PORT) and &cw(RMR_RTG_SVC)
+ be defined.
+ In the case where both variables are defined, RMR will behave exactly as is
+ communicated with the variable's values.
+ &half_space
+
+&ditem(RMR_RTG_SVC)
+ The value of this variable depends on the Route Manager in use.
+ &space
+ When the Route Manager is expecting to connect to an xAPP and push
+ route tables, this variable must indicate the &cw(port) which RMR should
+ use to listen for these connections.
+
+ &space
+ When the Route Manager is expecting RMR to connect and request a
+ table update during initialisation, the variable should be the
+ &cw(host:port) of the Route Manager process.
+
+ &space
+ The &cw(RMR_CTL_PORT) variable (added with the support of sending table update
+ requests to Route manager), controls the behaviour if this variable is not set.
+ See the description of that variable for details.
+ &half_space
+
+&ditem(RMR_HR_LOG)
+ By default RMR writes messages to standard error (incorrectly referred to as log messages)
+ in human readable format.
+ If this environment variable is set to 0, the format of standard error messages might
+ be written in some format not easily read by humans.
+ If missing, a value of 1 is assumed.
+ &half_space