From 127671fed1707e686e8d7b316b2641b663892fec Mon Sep 17 00:00:00 2001
From: Jan Gerhards <jan.p.gerhards@gmail.com>
Date: Wed, 15 May 2013 10:47:54 +0200
Subject: doc: describe relp tls parameters

---
 doc/imrelp.html | 5 ++++-
 doc/omrelp.html | 9 ++++++---
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/doc/imrelp.html b/doc/imrelp.html
index 9f3e4875..bcf52414 100644
--- a/doc/imrelp.html
+++ b/doc/imrelp.html
@@ -28,12 +28,15 @@ nits outlined above, is a much more reliable solution than plain tcp
 syslog and so it is highly suggested to use RELP instead of plain tcp.
 Clients send messages to the RELP server via omrelp.</p>
 
-<p><b>Configuration Directives</b>:</p>
+<p><b>Input Parameters</b>:</p>
 <ul>
 <li><b>Ruleset</b> &lt;name&gt;</br>
 Binds the specified ruleset to all RELP listeners.
 <li><b>Port</b> &lt;port&gt;<br>
 Starts a RELP server on selected port</li>
+<li><b>tls</b> (not mandatory, values "on","off", default "off")<br>
+	If set to "on", the RELP connection will be encrypted by TLS, 		so that the data is protected against observers. Please note 		that both the client and the server must have set TLS to 		either "on" or "off". Other combinations lead to unpredictable 		results.
+	</li>
 </ul>
 <b>Caveats/Known Bugs:</b>
 <ul>
diff --git a/doc/omrelp.html b/doc/omrelp.html
index 8858f884..e1f744cb 100644
--- a/doc/omrelp.html
+++ b/doc/omrelp.html
@@ -24,16 +24,19 @@ implementation).</p>
 rsyslog 7.3.10. For older versions, legacy configuration directives
 must be used.
 <ul>
-	<li><b>target </b>(mandatory)<br>
+	<li><b>target</b> (mandatory)<br>
 	The target server to connect to.
 	</li>
-	<li><b>template </b>(not mandatory, default "RSYSLOG_ForwardFormat")<br>
+	<li><b>template</b> (not mandatory, default "RSYSLOG_ForwardFormat")<br>
 	Defines the template to be used for the output.
 	</li>
-	<li><b>timeout </b>(not mandatory, default 90)<br>
+	<li><b>timeout</b> (not mandatory, default 90)<br>
 	Timeout for relp sessions. If set too low, valid sessions
 	may be considered dead and tried to recover.
 	</li>
+        <li><b>tls</b> (not mandatory, values "on","off", default "off")<br>
+	If set to "on", the RELP connection will be encrypted by TLS, 		so that the data is protected against observers. Please note 		that both the client and the server must have set TLS to 		either "on" or "off". Other combinations lead to unpredictable 		results.
+	</li>
 </ul>
 <p><b>Sample:</b></p>
 <p>The following sample sends all messages to the central server
-- 
cgit v1.2.3