diff options
author | Rainer Gerhards <rgerhards@adiscon.com> | 2008-02-13 17:56:46 +0000 |
---|---|---|
committer | Rainer Gerhards <rgerhards@adiscon.com> | 2008-02-13 17:56:46 +0000 |
commit | 96f394e67ebda80c123cc77948a94bee2178441d (patch) | |
tree | b85104651ef2cdc765c3eecd97f4f203af89a822 /doc | |
parent | 6831e4088656e145d442869b8ddc5ec9d3f65670 (diff) | |
download | rsyslog-96f394e67ebda80c123cc77948a94bee2178441d.tar.gz rsyslog-96f394e67ebda80c123cc77948a94bee2178441d.tar.xz rsyslog-96f394e67ebda80c123cc77948a94bee2178441d.zip |
created initial doc for imfile plugin
Diffstat (limited to 'doc')
-rw-r--r-- | doc/Makefile.am | 2 | ||||
-rw-r--r-- | doc/imfile.html | 65 | ||||
-rw-r--r-- | doc/rsyslog_ng_comparison.html | 650 |
3 files changed, 399 insertions, 318 deletions
diff --git a/doc/Makefile.am b/doc/Makefile.am index 8d126094..3bc63dbe 100644 --- a/doc/Makefile.am +++ b/doc/Makefile.am @@ -25,6 +25,8 @@ html_files = \ version_naming.html \ contributors.html \ dev_queue.html \ + omsnmp.html \ + imfile.html \ queues.html \ queueWorkerLogic.dia \ queueWorkerLogic.jpg \ diff --git a/doc/imfile.html b/doc/imfile.html new file mode 100644 index 00000000..6942b366 --- /dev/null +++ b/doc/imfile.html @@ -0,0 +1,65 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html><head> +<meta http-equiv="Content-Language" content="en"><title>Text File Input Monitor</title> + +</head> + +<body> +<h1>Text File Input Module</h1> +<p><b>Module Name: imfile</b></p> +<p><b>Author: </b>Rainer Gerhards +<rgerhards@adiscon.com></p> +<p><b>Description</b>:</p> +<p>Provides the ability to convert any standard text file into +a syslog message. A standard +text file is a file consisting of printable characters with lines +being delimited by LF.</p><p>The +file is read line-by-line and any line read is passed to rsyslog's rule +engine. The rule engine applies filter conditons and selects which +actions needs to be carried out.</p><p>As new lines are written they +are taken from the file and processed. Please note that this happens +based on a polling interval and not immediately. The file monitor +support file rotation. To fully work, rsyslogd must run while the file +is rotated. Then, any remaining lines from the old file are read and +processed and when done with that, the new file is being processed from +the beginning. If rsyslogd is stopped during rotation, the new file is +read, but any not-yet-reported lines from the previous file can no +longer be obtained.</p><p>When rsyslogd is stopped while monitoring a +text file, it records the last processed location and continues to work +from there upon restart. So no data is lost during a restart (except, +as noted above, if the file is rotated just in this very moment).</p><p>Currently, +the file must have a fixed name and location (directory). It is planned +to add support for dynamically generating file names in the future.</p><p>Multiple files may be monitored by specifying $InputRunFileMonitor multiple times. +</p> +<p><b>Configuration Directives</b>:</p> +<ul> +<li><strong>$InputFileName /path/to/file</strong><br> +The file being monitored. So far, this must be an absolute name (no macros or templates)</li><li><span style="font-weight: bold;">$InputFileTag tag:</span><br>The +tag to be used for messages that originate from this file. If you would +like to see the colon after the tag, you need to specify it here (as +shown above).</li><li><span style="font-weight: bold;">$InputFileStateFile <name-of-state-file></span><br>Rsyslog +must keep track of which parts of the to be monitored file it already +processed. This is done in the state file. This file always is created +in the rsyslog working directory (configurable via $WorkDirectory). Be +careful to use unique names for different files being monitored. If +there are duplicates, all sorts of "interesting" things may happen. +Rsyslog currently does not check if a name is specified multiple times.</li><li><span style="font-weight: bold;">$InputRunFileMonitor</span><br>This <span style="font-weight: bold;">activates</span> the current monitor. It has no parameters. If you forget this directive, no file monitoring will take place. +</li></ul><b>Caveats/Known Bugs:</b> +<p><b>Sample:</b></p> +<p>The following sample monitors a single file.<br></p> +<textarea rows="10" cols="60"> +ModLoad imfile.so +$InputFileName /path/to/file +$InputFileTag tag: +$InputFileStateFile file-in-workdir to keep status in +$InputRunFileMonitor </textarea> +<p>[<a href="rsyslog_conf.html">rsyslog.conf overview</a>] +[<a href="manual.html">manual index</a>] [<a href="http://www.rsyslog.com/">rsyslog site</a>]</p> +<p><font size="2">This documentation is part of the +<a href="http://www.rsyslog.com/">rsyslog</a> +project.<br> +Copyright © 2008 by <a href="http://www.gerhards.net/rainer">Rainer +Gerhards</a> and +<a href="http://www.adiscon.com/">Adiscon</a>. +Released under the GNU GPL version 3 or higher.</font></p> +</body></html>
\ No newline at end of file diff --git a/doc/rsyslog_ng_comparison.html b/doc/rsyslog_ng_comparison.html index 92c48399..b5ba79df 100644 --- a/doc/rsyslog_ng_comparison.html +++ b/doc/rsyslog_ng_comparison.html @@ -1,325 +1,339 @@ -<html> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html><head> +<meta http-equiv="Content-Language" content="de"><title>rsyslog vs. syslog-ng - a comparison</title> -<head> -<meta http-equiv="Content-Language" content="de"> -<title>rsyslog vs. syslog-ng - a comparison</title> </head> <body> - <h1>rsyslog vs. syslog-ng</h1> - - <P><small><i>Written by - - <a href="http://www.gerhards.net/rainer">Rainer - - Gerhards</a> (2008-01-29)</i></small></P> - -<p>We have often been asked abut a comparison sheet between rsyslog and -syslog-ng. Unfortunately, I do not know much about syslog-ng, I did not even use -it once. Also, there seems to be no comprehensive feature sheet available for -syslog-ng. So I started this comparison, but it probably is not complete. For -sure, I miss some syslog-ng features. This is not an attempt to let rsyslog -shine more than it should. I just used the <a href="features.html">rsyslog feature sheet</a> as a staring -point, simply because it was available. If you would like to add anything to the chart, or -correct it, please simply <a href="mailto:rgerhards@adiscon.com">drop me a line</a>. -I would love to see a real honest and up-to-date comparison sheet, so please -don't be shy ;)</p> +<p><small><i>Written by <a href="http://www.gerhards.net/rainer">Rainer Gerhards</a> +(2008-01-29)</i></small></p> +<p>We have often been asked abut a comparison sheet between +rsyslog and syslog-ng. Unfortunately, I do not know much about +syslog-ng, I did not even use it once. Also, there seems to be no +comprehensive feature sheet available for syslog-ng. So I started this +comparison, but it probably is not complete. For sure, I miss some +syslog-ng features. This is not an attempt to let rsyslog shine more +than it should. I just used the <a href="features.html">rsyslog +feature sheet</a> as a staring point, simply because it was +available. If you would like to add anything to the chart, or correct +it, please simply <a href="mailto:rgerhards@adiscon.com">drop +me a line</a>. I would love to see a real honest and up-to-date +comparison sheet, so please don't be shy ;)</p> <table border="1"> - <tr> - <td valign="top"><b>Feature</b></td> - <td valign="top"><b>rsyslog</b></td> - <td valign="top"><b>syslog-ng</b></td> - </tr> - <tr> - <td valign="top">native support for - <a href="http://www.rsyslog.com/doc-rsyslog_mysql.html">writing to MySQL - databases</a></td> - <td valign="top">yes</td> - <td valign="top">paid edition only</td> - </tr> - <tr> - <td valign="top">native support for writing to Postgres databases</td> - <td valign="top">yes</td> - <td valign="top">paid edition only</td> - </tr> - <tr> - <td valign="top">support for (plain) tcp based syslog</td> - <td valign="top">yes</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">support for sending and receiving compressed syslog messages</td> - <td valign="top">yes</td> - <td valign="top">I think "no"</td> - </tr> - <tr> - <td valign="top">support for on-demand on-disk spooling of messages</td> - <td valign="top">yes</td> - <td valign="top">paid edition only</td> - </tr> - <tr> - <td valign="top">ability to configure backup syslog/database servers </td> - <td valign="top">yes</td> - <td valign="top">no</td> - </tr> - <tr> - <td valign="top">support for receiving messages via reliable - <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC - 3195</a> delivery</td> - <td valign="top">yes</td> - <td valign="top">no</td> - </tr> - <tr> - <td valign="top">ability to generate file names and directories (log targets) - dynamically</td> - <td valign="top">yes</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">control of log output format, including ability to present channel - and priority as visible log data</td> - <td valign="top">yes</td> - <td valign="top">not sure...</td> - </tr> - <tr> - <td valign="top">good timestamp format control; at a minimum, ISO 8601/RFC 3339 - second-resolution UTC zone</td> - <td valign="top">yes</td> - <td valign="top">? (I guess so)</td> - </tr> - <tr> - <td valign="top">ability to reformat message contents and work with substrings</td> - <td valign="top">yes</td> - <td valign="top">I think yes</td> - </tr> - <tr> - <td valign="top">support for log files larger than 2gb</td> - <td valign="top">yes</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">support for file size limitation and automatic rollover command - execution</td> - <td valign="top">yes</td> - <td valign="top">yes (?)</td> - </tr> - <tr> - <td valign="top">support for running multiple rsyslogd instances on a single machine</td> - <td valign="top">yes</td> - <td valign="top">? (but I think yes)</td> - </tr> - <tr> - <td valign="top">support for - <a href="http://www.rsyslog.com/doc-rsyslog_stunnel.html">ssl-protected - syslog</a> </td> - <td valign="top">via stunnel</td> - <td valign="top">via stunnel<br> - paid edition natively</td> - </tr> - <tr> - <td valign="top">ability to filter on any part of the message, not just facility and - severity</td> - <td valign="top">yes</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">ability to use regular expressions in filters</td> - <td valign="top">yes</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">support for discarding messages based on filters</td> - <td valign="top">yes</td> - <td valign="top">?</td> - </tr> - <tr> - <td valign="top">ability to execute shell scripts on received messages</td> - <td valign="top">yes</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">ability to pipe messages to a continously running program</td> - <td valign="top">no</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">ability to preserve the original hostname in NAT environments and - relay chains</td> - <td valign="top">yes</td> - <td valign="top">yes (think so)</td> - </tr> - <tr> - <td valign="top">ability to limit the allowed network senders (syslog ACLs)</td> - <td valign="top">yes</td> - <td valign="top">yes (?)</td> - </tr> - <tr> - <td valign="top">powerful BSD-style hostname and program name blocks for easy - multi-host support</td> - <td valign="top">yes</td> - <td valign="top">no</td> - </tr> - <tr> - <td valign="top">massively multi-threaded for tomorrow's multi-core machines</td> - <td valign="top">yes</td> - <td valign="top">?</td> - </tr> - <tr> - <td valign="top">support for IETF's new syslog-protocol draft</td> - <td valign="top">yes</td> - <td valign="top">no</td> - </tr> - <tr> - <td valign="top">support for syslog-transport-tls based framing on syslog/tcp - connections</td> - <td valign="top">yes</td> - <td valign="top">no (?)</td> - </tr> - <tr> - <td valign="top">support for IPv6</td> - <td valign="top">yes</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">ability to control repeated line reduction ("last message repeated n - times") on a per selector-line basis</td> - <td valign="top">yes</td> - <td valign="top">yes (?)</td> - </tr> - <tr> - <td valign="top">ability to include config file from within other config - files</td> - <td valign="top">yes</td> - <td valign="top">no (?)</td> - </tr> - <tr> - <td valign="top">ability to include all config files existing in a - specific directory</td> - <td valign="top">yes</td> - <td valign="top">no (?)</td> - </tr> - <tr> - <td valign="top">supports multiple actions per selector/filter condition</td> - <td valign="top">yes</td> - <td valign="top">?</td> - </tr> - <tr> - <td valign="top">plug-in interface</td> - <td valign="top">yes</td> - <td valign="top">no (?)</td> - </tr> - <tr> - <td valign="top">Windows Event Log gatherer</td> - <td valign="top">via <a href="http://www.eventreporter.com">EventReporter</a> or - <a href="http://www.mwagent.com">MonitorWare Agent</a> (both commercial - software)</td> - <td valign="top">via Windows agent, paid edition only</td> - </tr> - <tr> - <td valign="top">config file format</td> - <td valign="top">compatible to legacy syslogd but ugly</td> - <td valign="top">clean but not backwards compatible</td> - </tr> - <tr> - <td valign="top">support for GSS-API</td> - <td valign="top">yes</td> - <td valign="top">?</td> - </tr> - <tr> - <td valign="top">web interface</td> - <td valign="top"><a href="http://www.phplogcon.org">phpLogCon</a><br> - [also works with <a href="http://freshmeat.net/projects/php-syslog-ng/"> - php-syslog-ng</a>]</td> - <td valign="top"><a href="http://freshmeat.net/projects/php-syslog-ng/"> - php-syslog-ng</a></td> - </tr> - <tr> - <td valign="top">using text files as input source</td> - <td valign="top">yes</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">native support for Oracle databases</td> - <td valign="top">no</td> - <td valign="top">paid edition only</td> - </tr> - <tr> - <td valign="top">native support for SQLite databases</td> - <td valign="top">no</td> - <td valign="top">paid edition only</td> - </tr> - <tr> - <td valign="top">rate-limiting output actions</td> - <td valign="top">yes</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">discard low-priority messages under system stress</td> - <td valign="top">yes</td> - <td valign="top">?</td> - </tr> - <tr> - <td valign="top" height="43">flow control (slow down message recpetion - when system is busy)</td> - <td valign="top" height="43">limited (TCP Window, delay on queue full)</td> - <td valign="top" height="43">yes (limited, too? "stops accepting - messages")</td> - </tr> - <tr> - <td valign="top">rewriting messages</td> - <td valign="top">yes</td> - <td valign="top">yes (at least I think so...)</td> - </tr> - <tr> - <td valign="top">output data into various formats</td> - <td valign="top">yes</td> - <td valign="top">yes (looks somewhat limited to me)</td> - </tr> - <tr> - <td valign="top">ability to control "message repeated n times" - generation</td> - <td valign="top">yes</td> - <td valign="top">no (?)</td> - </tr> - <tr> - <td valign="top">on the wire (zlib) message compression</td> - <td valign="top">yes</td> - <td valign="top">no (?)</td> - </tr> - <tr> - <td valign="top">license</td> - <td valign="top">GPLv3 (GPLv2 for v2 branch)</td> - <td valign="top">GPL (paid edition is closed source)</td> - </tr> - <tr> - <td valign="top">supported platforms</td> - <td valign="top">Linux, BSD, anecdotical seen on Solaris</td> - <td valign="top">many popular *nixes</td> - </tr> - <tr> - <td valign="top">DNS cache</td> - <td valign="top">no</td> - <td valign="top">yes</td> - </tr> - <tr> - <td valign="top">native ability to send SNMP traps</td> - <td valign="top">yes</td> - <td valign="top">?</td> - </tr> - <tr> - <td valign="top">? (probably many I do no know off...)</td> - <td valign="top">no</td> - <td valign="top">yes</td> - </tr> +<tbody> +<tr> +<td valign="top"><b>Feature</b></td> +<td valign="top"><b>rsyslog</b></td> +<td valign="top"><b>syslog-ng</b></td> +</tr> +<tr> +<td valign="top">native support for <a href="http://www.rsyslog.com/doc-rsyslog_mysql.html">writing +to MySQL databases</a></td> +<td valign="top">yes</td> +<td valign="top">paid edition only</td> +</tr> +<tr> +<td valign="top">native support for writing to +Postgres databases</td> +<td valign="top">yes</td> +<td valign="top">paid edition only</td> +</tr> +<tr> +<td valign="top">support for (plain) tcp based syslog</td> +<td valign="top">yes</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">support for sending and receiving +compressed syslog messages</td> +<td valign="top">yes</td> +<td valign="top">I think "no"</td> +</tr> +<tr> +<td valign="top">support for on-demand on-disk +spooling of messages</td> +<td valign="top">yes</td> +<td valign="top">paid edition only</td> +</tr> +<tr> +<td valign="top">ability to configure backup +syslog/database servers </td> +<td valign="top">yes</td> +<td valign="top">no</td> +</tr> +<tr> +<td valign="top">support for receiving messages via +reliable <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC +3195</a> delivery</td> +<td valign="top">yes</td> +<td valign="top">no</td> +</tr> +<tr> +<td valign="top">ability to generate file names and +directories (log targets) dynamically</td> +<td valign="top">yes</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">control of log output format, +including ability to present channel and priority as visible log data</td> +<td valign="top">yes</td> +<td valign="top">not sure...</td> +</tr> +<tr> +<td valign="top">good timestamp format control; at a +minimum, ISO 8601/RFC 3339 second-resolution UTC zone</td> +<td valign="top">yes</td> +<td valign="top">? (I guess so)</td> +</tr> +<tr> +<td valign="top">ability to reformat message +contents and work with substrings</td> +<td valign="top">yes</td> +<td valign="top">I think yes</td> +</tr> +<tr> +<td valign="top">support for log files larger than +2gb</td> +<td valign="top">yes</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">support for file size limitation +and automatic rollover command execution</td> +<td valign="top">yes</td> +<td valign="top">yes (?)</td> +</tr> +<tr> +<td valign="top">support for running multiple +rsyslogd instances on a single machine</td> +<td valign="top">yes</td> +<td valign="top">? (but I think yes)</td> +</tr> +<tr> +<td valign="top">support for <a href="rsyslog_stunnel.html">ssl-protected +syslog</a> </td> +<td valign="top"><a href="rsyslog_stunnel.html">via +stunnel</a></td> +<td valign="top">via stunnel<br> +paid edition natively</td> +</tr> +<tr> +<td valign="top">ability to filter on any part of +the message, not just facility and severity</td> +<td valign="top">yes</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">ability to use regular expressions +in filters</td> +<td valign="top">yes</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">support for discarding messages +based on filters</td> +<td valign="top">yes</td> +<td valign="top">?</td> +</tr> +<tr> +<td valign="top">ability to execute shell scripts on +received messages</td> +<td valign="top">yes</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">ability to pipe messages to a +continously running program</td> +<td valign="top">no</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">ability to preserve the original +hostname in NAT environments and relay chains</td> +<td valign="top">yes</td> +<td valign="top">yes (think so)</td> +</tr> +<tr> +<td valign="top">ability to limit the allowed +network senders (syslog ACLs)</td> +<td valign="top">yes</td> +<td valign="top">yes (?)</td> +</tr> +<tr> +<td valign="top">powerful BSD-style hostname and +program name blocks for easy multi-host support</td> +<td valign="top">yes</td> +<td valign="top">no</td> +</tr> +<tr> +<td valign="top">massively multi-threaded for +tomorrow's multi-core machines</td> +<td valign="top">yes</td> +<td valign="top">?</td> +</tr> +<tr> +<td valign="top">support for IETF's new +syslog-protocol draft</td> +<td valign="top">yes</td> +<td valign="top">no</td> +</tr> +<tr> +<td valign="top">support for syslog-transport-tls +based framing on syslog/tcp connections</td> +<td valign="top">yes</td> +<td valign="top">no (?)</td> +</tr> +<tr> +<td valign="top">support for IPv6</td> +<td valign="top">yes</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">ability to control repeated line +reduction ("last message repeated n times") on a per selector-line basis</td> +<td valign="top">yes</td> +<td valign="top">yes (?)</td> +</tr> +<tr> +<td valign="top">ability to include config file from +within other config files</td> +<td valign="top">yes</td> +<td valign="top">no (?)</td> +</tr> +<tr> +<td valign="top">ability to include all config files +existing in a specific directory</td> +<td valign="top">yes</td> +<td valign="top">no (?)</td> +</tr> +<tr> +<td valign="top">supports multiple actions per +selector/filter condition</td> +<td valign="top">yes</td> +<td valign="top">?</td> +</tr> +<tr> +<td valign="top">plug-in interface</td> +<td valign="top">yes</td> +<td valign="top">no (?)</td> +</tr> +<tr> +<td valign="top">Windows Event Log gatherer</td> +<td valign="top">via <a href="http://www.eventreporter.com">EventReporter</a> +or <a href="http://www.mwagent.com">MonitorWare Agent</a> +(both commercial software)</td> +<td valign="top">via Windows agent, paid edition only</td> +</tr> +<tr> +<td valign="top">config file format</td> +<td valign="top">compatible to legacy syslogd but +ugly</td> +<td valign="top">clean but not backwards compatible</td> +</tr> +<tr> +<td valign="top">support for GSS-API</td> +<td valign="top">yes</td> +<td valign="top">?</td> +</tr> +<tr> +<td valign="top">web interface</td> +<td valign="top"><a href="http://www.phplogcon.org">phpLogCon</a><br> +[also works with <a href="http://freshmeat.net/projects/php-syslog-ng/"> +php-syslog-ng</a>]</td> +<td valign="top"><a href="http://freshmeat.net/projects/php-syslog-ng/"> +php-syslog-ng</a></td> +</tr> +<tr> +<td valign="top">using text files as input source</td> +<td valign="top">yes</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">native support for Oracle databases</td> +<td valign="top">no</td> +<td valign="top">paid edition only</td> +</tr> +<tr> +<td valign="top">native support for SQLite databases</td> +<td valign="top">no</td> +<td valign="top">paid edition only</td> +</tr> +<tr> +<td valign="top">rate-limiting output actions</td> +<td valign="top">yes</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">discard low-priority messages under +system stress</td> +<td valign="top">yes</td> +<td valign="top">?</td> +</tr> +<tr> +<td height="43" valign="top">flow control +(slow down message recpetion when system is busy)</td> +<td height="43" valign="top">limited (TCP +Window, delay on queue full)</td> +<td height="43" valign="top">yes (limited, +too? "stops accepting messages")</td> +</tr> +<tr> +<td valign="top">rewriting messages</td> +<td valign="top">yes</td> +<td valign="top">yes (at least I think so...)</td> +</tr> +<tr> +<td valign="top">output data into various formats</td> +<td valign="top">yes</td> +<td valign="top">yes (looks somewhat limited to me)</td> +</tr> +<tr> +<td valign="top">ability to control "message +repeated n times" generation</td> +<td valign="top">yes</td> +<td valign="top">no (?)</td> +</tr> +<tr> +<td valign="top">on the wire (zlib) message +compression</td> +<td valign="top">yes</td> +<td valign="top">no (?)</td> +</tr> +<tr> +<td valign="top">license</td> +<td valign="top">GPLv3 (GPLv2 for v2 branch)</td> +<td valign="top">GPL (paid edition is closed source)</td> +</tr> +<tr> +<td valign="top">supported platforms</td> +<td valign="top">Linux, BSD, anecdotical seen on +Solaris</td> +<td valign="top">many popular *nixes</td> +</tr> +<tr> +<td valign="top">DNS cache</td> +<td valign="top">no</td> +<td valign="top">yes</td> +</tr> +<tr> +<td valign="top">native ability to send SNMP traps</td> +<td valign="top">yes</td> +<td valign="top">?</td> +</tr> +<tr> +<td valign="top">? (probably many I do no know +off...)</td> +<td valign="top">no</td> +<td valign="top">yes</td> +</tr> +</tbody> </table> -<p>Based on a discussion I had, I also wrote about the <b>political argument why -it is good to have another strong syslogd besides syslog-ng</b>. You may want to -read it at my blog at "<a href="http://rgerhards.blogspot.com/2007/08/why-does-world-need-another-syslogd.html">Why -does the world need another syslogd?</a>".</p> -<p>This document is current as of 2008-02-11 and definitely incomplete (I did -not yet manage to complete it!).</p> - -</body> - -</html> +<p>Based on a discussion I had, I also wrote about the <b>political +argument why it is good to have another strong syslogd besides syslog-ng</b>. +You may want to read it at my blog at "<a href="http://rgerhards.blogspot.com/2007/08/why-does-world-need-another-syslogd.html">Why +does the world need another syslogd?</a>".</p> +<p>This document is current as of 2008-02-11 and definitely +incomplete (I did not yet manage to complete it!).</p> +</body></html>
\ No newline at end of file |