-Providing A Static Table
-========================
-
-For testing, or possibly bootstrapping purposes, a static
-route table can be supplied. During initialisation, RMR will
-check the ``RMR_SEED_RT`` environment variable. If it exists,
-and references a file, RMR will open and read the file
-expecting to find a static route table. This route table is
-used until an update is received from a *Route Manager*.
-Normally, when the RMR initialisation function is invoked, a
-listener is started to receive route table information from a
-route manager process. During testing it is often useful to
-supply a static table which is available should no route
-management process exist, or to provide a seed table to use
-before the first table is delivered. The environment variable
-``RMR_SEED_RT`` can be set to provide the RMR initialisation
-function with the name of the static table to use. If a
-static table is provided, it will be loaded only once, and
-will be overlaid if a dynamically delivered table is
-received.
+Using A Static Route Table
+--------------------------
+
+A static route table can be provided to assist with testing,
+or to provide a bootstrap set of route information until a
+dynamic table is received from a routing manager. The
+environment variable ``RMR_SEED_RT`` is checked during RMR
+initialisation and if set is expected to reference a file
+containing a route table. This table will be loaded and used
+until overlaid by a table sent by the *Route Manager*.
+
+For testing, the static table will be reloaded periodically
+if the ``RMR_RTG_SVC`` environment variable is set to -1.
+When this testing feature is enabled RMR will not listen for
+*Route Manager* connections, nor will it attempt to request a
+dynamic table.