rsyslog/rsyslog
1
0
Fork 0
mirror of https://github.com/rsyslog/rsyslog.git synced 2025-12-19 20:50:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

doc updates for release 1.14.0

Browse Source
This commit is contained in:
Rainer Gerhards 2007-06-28 06:50:57 +00:00
parent 56c8bd7bde
commit 2a98edf43b
3 changed files with 107 additions and 104 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/bugs.html
View File

@ -9,23 +9,23 @@ we also have a
<a href="http://sourceforge.net/tracker/?atid=696552&group_id=123448&func=browse">
bug tracker at sourceforge.net</a>. This list here contains more architectural
things while the bug tracker most often lists things that you will actually
experience. I am working to combine the two lists, but for now you need to visit
both.</p>
<p>This list has last been updated on 2005-09-26 by
experience. Please be sure to visit the bug tracker in addition to this list
here.</p>
<p>This list has last been updated on 2007-06-28 by
<a href="http://www.adiscon.com/en/people/rainer-gerhards.php">Rainer Gerhards</a>.</p>
<h1>rsyslogd</h1>
<h2>IPv6</h2>
<p>IPv6 is currently supported for UDP, only. TCP support is to follow.</p>
<h2>AllowedSender and IPv6</h2>
<p>AllowedSenders currently can be used with IPv4, only. IPv6 senders are always
allowed. If you need access control for IPv6, use iptables. AllowedSender
support for IPv6 will most probably be added. Please note that you can also
disable IPv6 support by specifying -4 on the command line.</p>
<h2>REPEATED LOG LINES</h2>
<p>If multiple log lines with the exact same content are received,
the duplicates are NOT suppressed. This is done by sysklogd
in all cases. We plan to add this as an optional feature,
but as of now every line is logged.</p>
<h2>ERRORS ON STARTUP</h2>
<p>Error reporting on startup is not particular good. We handle all
errors correctly, but sometimes a message is only reported if
running in debug mode. If you experience some strange behaviour
I suggest to run the syslogd interactively with debugging enabled.
As of August, 2005, the situation has much improved. Keep in mind,
thought, that debug mode is your friend ;)</p>
<h2>EQUALLY-NAMED TEMPLATES</h2>
<p>If multiple templates with the SAME name are created, all but the
first definition is IGNORED. So you can NOT (yet) replace a

13
doc/features.html
View File

@ -27,19 +27,22 @@ is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mai
messages<li>control of whether the local hostname or the hostname of the
origin of the data is shown as the hostname in the output<li>ability to
preserve the original hostname in NAT environments and relay chains
<li>ability to limit the allowed network senders<li>powerful BSD-style hostname and program name blocks for easy multi-host support<li> multi-threaded - currently experimental<li>very experimental and volatile support for <a href="syslog-protocol.html">syslog-protocol</a> compliant messages (it is volatile because standardization is currently underway and this is a proof-of-concept implementation to aid this effort)<li>
<li>ability to limit the allowed network senders<li>powerful BSD-style hostname and program name blocks for easy multi-host support<li> multi-threaded<li>very experimental and volatile support for <a href="syslog-protocol.html">syslog-protocol</a> compliant messages (it is volatile because standardization is currently underway and this is a proof-of-concept implementation to aid this effort)<li>
experimental support for syslog-transport-tls based framing on syslog/tcp
connections<li>
a copy of klogd.c has been included under the name of rklogd for those Linux
systems that need one. So rsyslog is a full replacement for the sysklogd
package</ul>
package<li>
support for IPv6 (currently UDP only, but TCP will be added soon)</ul>
<p>&nbsp;</p>
<h2>Upcoming Features</h2>
<ul>
<li>support for native SSL enryption of plain tcp syslog sessions. This will
most probably happen based on syslog-transport-tls.<li>even more enhanced multi-threading<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. So far, this seems sufficient so that there is no urgent</ul>
<p>&nbsp;</p>
most probably happen based on syslog-transport-tls.<li>even more enhanced multi-threading<li>pcre filtering - maybe (depending on feedback)&nbsp; - simple regex already
partly added. So far, this seems sufficient so that there is no urgent<li>support for <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a> as a sender - this is currently unlikely to happen, because there is no real
demand for it. Any work on RFC 3195 has been suspend until we see some real
interest in it.&nbsp; It is probably much better to use TCP-based syslog,
which is interoprable with a large number of applications.</ul>
<p>To see when each feature was added, see the
<a href="http://www.rsyslog.com/Topic4.phtml">rsyslog change log</a> (online
only).</p>

6
doc/status.html
View File

@ -4,10 +4,10 @@
</head>
<body>
<h2>rsyslog status page</h2>
<p>This page reflects the status as of 2007-06-22.</p>
<p>This page reflects the status as of 2007-06-28.</p>
<h2>Current Releases</h2>
<p><b>development:</b> 1.13.5 - <a href="http://www.rsyslog.com/Article74.phtml">change log</a> -
<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-34.phtml">download</a></p>
<p><b>development:</b> 1.14.0 - <a href="http://www.rsyslog.com/Article76.phtml">change log</a> -
<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-35.phtml">download</a></p>
<p><b>stable:</b> 1.0.4 - <a href="http://www.rsyslog.com/Article54.phtml">change log</a> -
<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-26.phtml">download</a></p>
<p>&nbsp;(<a href="version_naming.html">How are versions named?</a>)</p>