diff options
Diffstat (limited to 'doc/features.html')
| -rw-r--r-- | doc/features.html | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/doc/features.html b/doc/features.html index a3b119cc..378c298d 100644 --- a/doc/features.html +++ b/doc/features.html @@ -37,7 +37,9 @@ is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mai package<li> support for IPv6<li> ability to control repeated line reduction ("last message repeated n times") - on a per selector-line basis</ul> + on a per selector-line basis<li> + supports sub-configuration files, which can be automatically read from + directories. Includes are specified in the main configuration file</ul> <p> </p> <h2>Upcoming Features</h2> <p>The list below is something like a repository of ideas we'd like to @@ -50,7 +52,8 @@ reach of implementation. Users are encouraged to submit feature requests there 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<li>implement native email-functionality in + <li>create a plug-in-interface - we are very close to this. A neat interface is + already used internally for output modules.<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 @@ -59,7 +62,8 @@ at some time moved back to the sourceforge tracker.</p> with a message queue for each selector line (when implementing this, search for CHECKMULTIQUEUE comments in the source - they already contain hints of what to look at).<li>pcre filtering - maybe (depending on feedback) - 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 + 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 interoprable with a large number of applications.</ul> |