updated doc to reflect 1.11.0

4 files changed, 15 insertions, 12 deletions

diff --git a/doc/features.html b/doc/features.html
index 0624e503..6f7f6af7 100644
--- a/doc/features.html
+++ b/doc/features.html
@@ -14,7 +14,7 @@ is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mai
 <ul>


 


  <li>native support for <a href="rsyslog_mysql.html">writing to MySQL databases</a><li>support for (plain) tcp 


-	based syslog - much better reliability<li>control of log output format, 


+	based syslog - much better reliability<li>support for receiving messages via 
	reliable <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">
	RFC 3195</a> delivery<li>control of log output format, 


 	including ability to present channel and priority as visible log data<li>good timestamp format control; at a minimum, ISO 8601/RFC 3339


  second-resolution UTC zone<li>ability to reformat message contents and work with substrings<li>support for 


 	log files larger than 2gb<li>support for file size limitation and automatic 


@@ -33,8 +33,7 @@ is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mai
 	<a href="http://www.syslog.cc/ietf/drafts/draft-ietf-syslog-protocol-14.txt">


 	syslog-protocol-14</a> compliant messages 


 	(pending, as IETF will change proposed format)<li>support for native SSL enryption of plain tcp syslog sessions


-	<li>RFC 3195 support - planned (but late)


- 	<li>pcre filtering - maybe (depending on feedback)&nbsp; - simple regex already 


+	<li>support for
	<a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a> 
	as a sender - planned<li>pcre filtering - maybe (depending on feedback)&nbsp; - simple regex already 


 	partly added


  	<li>multi-threaded redesign - maybe (depending on feedback; also


  opens Pandorra's cross-platform development box ;))


diff --git a/doc/history.html b/doc/history.html
index d40d13ca..91ee4909 100644
--- a/doc/history.html
+++ b/doc/history.html
@@ -30,8 +30,10 @@ places indicated that RFC3195 is NOT a prime priority for users, but
 rather better control over the output format. So here we are, with

 a rsyslod that covers a lot of enhancements, but not a single one

 of these that made its name ;) Since version 0.9.2, receiving syslog messages 

-via plain tcp is finally supported, bringing rsyslogd a bit closer to its name.

-</p><p>

+via plain tcp is finally supported, a bit later sending via TCP, too. Starting 

+with 1.11.0, RFC 3195 is finally support at the receiving side (a.k.a. &quot;listener&quot;). 

+Support for sending via RFC 3195 is still due. Anyhow, rsyslog has come much 

+closer to what it name promises.</p><p>

 The next enhancement scheduled is support for the new syslog-protocol

 internet draft format, not the least to see how easy/complicated it is

 to implement. We already know that some subleties of syslog-protocol will

@@ -42,7 +44,7 @@ we intend to advance the code and introduce new features.
 </p><p>

 The database support was included so that our web-based syslog interface

 can be used. This is another open source project which can be found

-under <a href="http://www.liblogging.org/">http://www.liblogging.org</a>. We highly recommend having a look at 

+under <a href="http://www.phplogcon.org">http://www.phplogcon.org</a>. We highly recommend having a look at 

 it. It might not work for you if you expect thousands of messages per

 second (because your database won't be able to provide adequate performance),

 but in many cases it is a very handy analysis and troubleshooting tool.

@@ -60,8 +62,10 @@ sizes of 32k and more. This feature has been tested, but by default is turned of
 (as it has some memory footprint that we didn't want to put on users not 

 actually requiring it). Search the file syslogd.c and search for &quot;IHE&quot; - you 

 will find easy and precise instructions on what you need to change (it's just 

-one line of code!).

-<p>Be sure to visit Rainer's <a href="http://rgerhards.blogspot.com/">syslog block</a>

+one line of code!). Please note that RFC 3195/COOKED supports 1K message sizes 

+only. It'll probably support longer messages in the future, but it is our 

+believe that using larger messages with current RFC 3195 is a violation of the 

+standard.<p>Be sure to visit Rainer's <a href="http://rgerhards.blogspot.com/">syslog block</a>

 to get some more insight into the development of rsyslog and syslog in general.</p>

 <h2>Some useful links</h2>

 <ul>

diff --git a/doc/rsyslog_stunnel.html b/doc/rsyslog_stunnel.html
index 71bb878d..9d944521 100644
--- a/doc/rsyslog_stunnel.html
+++ b/doc/rsyslog_stunnel.html
@@ -209,7 +209,7 @@ security-sensitve, you should have a look at the various stunnel settings that
 help you further secure the system.</P>

 <h2>Preventing Systems from talking directly to the rsyslog Server</h2>

 <P>It is possible that remote systems (or attackers) talk to the rsyslog server 

-by directly connecting to its port 61514. Currently (Jule of 2005), rsyslog does 

+by directly connecting to its port 61514. Currently (July of 2005), rsyslog does 

 not offer the ability to bind to the local host, only. This feature is planned, 

 but as long as it is missing, rsyslog must be protected via a firewall. This can 

 easily be done via e.g iptables. Just be sure not to forget it.</P>

diff --git a/doc/status.html b/doc/status.html
index 6378c2cb..92e13965 100644
--- a/doc/status.html
+++ b/doc/status.html
@@ -4,10 +4,10 @@
 </head>

 <body>

 <h2>rsyslog status page</h2>

-<p>This page reflects the status as of 2005-09-27.</p>

+<p>This page reflects the status as of 2005-10-12.</p>

 <h2>Current Releases</h2>

-<p><b>development:</b> 1.10.2 - <a href="http://www.rsyslog.com/Article38.phtml">change log</a> -

-<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-19.phtml">download</a></p>

+<p><b>development:</b> 1.11.0 - <a href="http://www.rsyslog.com/Article41.phtml">change log</a> -

+<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-21.phtml">download</a></p>

 <p><b>stable:</b> 1.0.2 - <a href="http://www.rsyslog.com/Article40.phtml">change log</a> -

 <a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-20.phtml">download</a></p>

 <p>&nbsp;(<a href="version_naming.html">How are versions named?</a>)</p>