Add safe connect, fix possible seg fault in RTC
This change adds "safe connect" to the SI95 code which avoids
the connect to even port bug in Linux which could potentially
result in a successful connection when the remote process is
not running or listening on the attempted port.
Issue-ID: RIC-332
This change also includes a change to the level 2 debugging
in the route table collector (RTC) code which could have
resulted in a segment fault.
Issue-ID: RIC-335
Several of the man pages are updated with typo corrections.
Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: Ib6045f36850bd2a4b07a19bf11839ce3e9824b6a
diff --git a/docs/rmr_get_src.3.rst b/docs/rmr_get_src.3.rst
index 5202fc0..d76e5a0 100644
--- a/docs/rmr_get_src.3.rst
+++ b/docs/rmr_get_src.3.rst
@@ -36,14 +36,14 @@
The rmr_get_src function will copy the *source* information
from the message to a buffer (dest) supplied by the user. In
-an RMr message, the source is the sender's information that
+an RMR message, the source is the sender's information that
is used for return to sender function calls, and is generally
the hostname and port in the form *name*. The source might be
an IP address port combination; the data is populated by the
sending process and the only requirement is that it be
capable of being used to start a TCP session with the sender.
-The maximum size allowed by RMr is 64 bytes (including the
+The maximum size allowed by RMR is 64 bytes (including the
nil string terminator), so the user must ensure that the
destination buffer given is at least 64 bytes.