From aba90e82484118f3568ec51c01de5ba845da589a Mon Sep 17 00:00:00 2001
From: Rainer Gerhards
Date: Fri, 22 May 2009 17:06:52 +0200
Subject: added capability to run multiple tcp listeners (on different ports)
Well, actually this and a lot of related things. I improved the
testbench so that the new capabilities are automatically tested and
also did some general cleanup. The current multiple tcp listener
solution will probably receive some further cleanup, too, but looks
quite OK so far. I also reviewed the way tcpsrv et all work, in
preparation of using this code for imdiag. I need to document the
findings, especially as the code is rather complicated "thanks" to
the combination of plain tcp and gssapi transport modes.
---
doc/imtcp.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
(limited to 'doc/imtcp.html')
diff --git a/doc/imtcp.html b/doc/imtcp.html
index 0ee0f96a..9ea7efa1 100644
--- a/doc/imtcp.html
+++ b/doc/imtcp.html
@@ -14,9 +14,10 @@ Encryption can be provided by using stunnel
(an alternative is the use
the imgssapi
modul).
-In the future, multiple receivers may be configured by
+
Multiple receivers may be configured by
specifying
-$InputTCPServerRun multiple times. This is not currently supported.
+$InputTCPServerRun multiple times. This is available since version 4.3.1, earlier
+versions do NOT support it.
Configuration Directives:
@@ -58,7 +59,6 @@ AuthMode and network stream driver. Permitted
Caveats/Known Bugs:
- module always binds to all interfaces
-- only a single listener can be bound
- can not be loaded together with imgssapi
(which includes the functionality of imtcp)
--
cgit