diff options
| -rw-r--r-- | doc/bugs.html | 39 | ||||
| -rw-r--r-- | doc/features.html | 34 |
2 files changed, 11 insertions, 62 deletions
diff --git a/doc/bugs.html b/doc/bugs.html index 8f775600..a12c43f3 100644 --- a/doc/bugs.html +++ b/doc/bugs.html @@ -4,37 +4,14 @@ </head> <body> <h1>rsyslog bugs and annoyances</h1> -<p><b>This page lists the known bugs rsyslog has to offer.</b> Please note that -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. Please be sure to visit the bug tracker in addition to this list -here.</p> -<p>This list has last been updated on 2007-07-30 by +<p><b>This page lists the known bugs rsyslog has to offer.</b> It lists +old and esoteric bugs. A live list of bugs is contained in our bugzilla. <b> +<font color="#FF0000">Please visit </font><a href="http://www.rsyslog.com/bugs"> +<font color="#FF0000">http://www.rsyslog.com/bugs</font></a></b> to see what we +have. There, you can also open your own bug report if you think you found one.</p> +<p>This list has last been updated on 2008-02-12 by <a href="http://www.adiscon.com/en/people/rainer-gerhards.php">Rainer Gerhards</a>.</p> <h1>rsyslogd</h1> -<h2>stability in multithreaded mode</h2> -<p>We have some reports that rsyslogd, if compiled with multi-threading enabled, -segfaults in some environments. We are actively looking at fixing this issue, -but as it does not occur in our lab environment, that unfortunately takes some -time. If you experience a segfault, please report it. As a work-around, you can -compile rsyslog without multi-threading:</p> -<p>./configure --disable-pthreads<br> -make clean<br> -make<br> -make install</p> -<p>This somewhat reduces the ability to handle large message bursts, but even in -single-threaded mode rsyslogd offers great performance (just think that stock -sysklogd has always been using a single thread, only).</p> -<h2>forwarding remotely received messages</h2> -<p>Sysklogd does not forward remotely received messages to other network -destination except when the -h option is given. This code is currently defunct. -No matter if -h is specified or not, messages are ALWAYS forwarded. It is -currently under review if the sysklogd's functionality is actually needed. -Please see my -<a href="http://rgerhards.blogspot.com/2007/07/on-syslogd-h-option.html">blog -post on this topic</a> for further detail.</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 @@ -46,10 +23,6 @@ names...).</p> <p>This format is actually not 100% compatible with stock syslogd - the date is missing. Will be fixed soon and can also be fixed just via the proper template. Anyone up for this? ;)</p> -<h2>SIGPIPE HANDLING</h2> -<p>Currently, SIGPIPE is ignored. This is necessary to handle broken TCP - connections. We should further look into this issue and see which other - ways exist to handle the situation.</p> <h2>MULTIPLE INSTANCES</h2> <p>If multiple instances are running on a single machine, the one with the -r switch must start first. Also, UDP-based syslog forwarding between the diff --git a/doc/features.html b/doc/features.html index 2899cd76..c71194dc 100644 --- a/doc/features.html +++ b/doc/features.html @@ -53,36 +53,12 @@ is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mai <p>The list below is something like a repository of ideas we'd like to implement. Features on this list are typically NOT scheduled for immediate inclusion. We maintain a -<a href="http://sourceforge.net/tracker/?group_id=123448&atid=696555">feature -request tracker at sourceforge.net</a>. This tracker has things typically within +<a href="http://bugzilla.adiscon.com/rsyslog-feature.html">feature +request tracker at our bugzilla</a>. This tracker has things typically within reach of implementation. Users are encouraged to submit feature requests there -(or via our forums). If we like them but they look quite long-lived (aka "not -soon to be implemented"), they will possibly be migrated to this list here and -at some time moved back to the sourceforge tracker.</p> -<ul> - <li>create a plug-in-interface - we are very close to this. A neat interface is - already used internally for output modules and the MySQL module already - works as a plug-in. However, no interface definition is yet formally - published.<li>implement native email-functionality in - selector (probably best done as a plug-in)<li>port it to more *nix variants - (eg AIX and HP UX) - this needs volunteers with access to those machines and - knowledge<li>provide an on-disk queue for syslog messages; should be - combined with reliable delivery to the next hop<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, - with a message queue for each action (when implementing this, search - for CHECKMULTIQUEUE comments in the source - they already contain hints of - what to look at). Some detail information on this can already be found in - <a href="http://rgerhards.blogspot.com/2007/08/syslog-worker-pools-future-hardware-and.html"> - Rainer's blog</a>.<li>pcre filtering - maybe (depending on feedback) - simple regex already - partly added. So far, this seems sufficient so that there is no urgent need - to do pcre<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. It is probably much better to use TCP-based syslog, - which is interoperable with a large number of applications. You may also - read my blog post on the future of liblogging, which contains interesting - information about the - <a href="http://rgerhards.blogspot.com/2007/09/where-is-liblogging-heading-to.html"> - future of RFC 3195 in rsyslog</a>.</ul> +(or via our forums). <b>Please note that rsyslog v2 is feature-complete. New +features will be implemented in the v3 branch only. </b>Version 3 already has a +number of very exciting additional features.</p> <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> |