diff options
| -rw-r--r-- | NEWS | 15 | ||||
| -rw-r--r-- | doc/features.html | 8 | ||||
| -rw-r--r-- | doc/history.html | 154 | ||||
| -rw-r--r-- | doc/rsyslog_packages.html | 68 | ||||
| -rw-r--r-- | doc/status.html | 10 | ||||
| -rw-r--r-- | rsyslogd.8 | 26 |
6 files changed, 148 insertions, 133 deletions
@@ -1,7 +1,20 @@ --------------------------------------------------------------------------- -Version 1.15.1 (RGer), 2007-07-0? +Version 1.15.1 (RGer), 2007-07-10 - fixed a bug that caused a dynaFile selector to stall when there was an open error with one file +- improved template processing for dynaFiles; templates are now only + looked up during initialization - speeds up processing +- optimized memory layout in struct filed when compiled with MySQL + support +- fixed a bug that caused compilation without SYSLOG_INET to fail +- re-enabled the "last message repeated n times" feature. This + feature was not taken care of while rsyslogd evolved from sysklogd + and it was more or less defunct. Now it is fully functional again. +- added system properties: $NOW, $YEAR, $MONTH, $DAY, $HOUR, $MINUTE +- fixed a bug in iovAsString() that caused a memory leak under stress + conditions (most probably memory shortage). This was unlikely to + ever happen, but it doesn't hurt doing it right +- cosmetic: defined type "uchar", change all unsigned chars to uchar --------------------------------------------------------------------------- Version 1.15.0 (RGer), 2007-07-05 - added ability to dynamically generate file names based on templates diff --git a/doc/features.html b/doc/features.html index 7a690ae7..611e8403 100644 --- a/doc/features.html +++ b/doc/features.html @@ -50,8 +50,12 @@ at some time moved back to the sourceforge tracker.</p> <li>create a plug-in-interface<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>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>pcre filtering - maybe (depending on feedback) - simple regex already + 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 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 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, diff --git a/doc/history.html b/doc/history.html index 91ee4909..02dec93c 100644 --- a/doc/history.html +++ b/doc/history.html @@ -1,75 +1,81 @@ -<html>
-<head>
-<title>rsyslog history</title>
-</head>
-<body>
-<h1>RSyslog - History</h1>
-
-<b>Rsyslog is a GPL-ed, enhanced syslogd. Among others, it offers support for
-reliable syslog over TCP, writing to
-MySQL databases and fully configurable output formats (including great timestamps).</b>
-Rsyslog was initiated by Rainer Gerhards. It has
-been forked from the <a href="http://www.infodrom.org/projects/sysklogd/">sysklogd standard package</a>.
-The goal of the
-rsyslog project is to provide a more configurable and reliable
-syslog deamon while retaining drop-in replacement capabilities for stock syslogd. By "reliable", we mean support for reliable transmission
-modes like TCP or <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a> (syslog-reliable).
-We do NOT imply that the sysklogd package is unreliable. In fact, the
-opposite is the case and we assume that for the time being the well-used
-sysklogd package offers better program reliability than our
-brand-new modifications to it.
-
-</p><p>The name "rsyslog" stems back to the
-planned support for syslog-reliable. Ironically, the initial release
-of rsyslog did NEITHER support syslog-reliable NOR tcp based syslog.
-Instead, it contains enhanced configurability and other enhancements
-(like database support). The reason for this is that full support for
-RFC 3195 would require even more changes and especially fundamental architectural
-changes. Also, questions asked on the loganalysis list and at other
-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, a bit later sending via TCP, too. Starting
-with 1.11.0, RFC 3195 is finally support at the receiving side (a.k.a. "listener").
-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
-require at least one considerable architectural change to the syslogd
-and this might delay things a little. Our immediate goal is to receive
-feedback and get the bugs out of the current release. Only after that
-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.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.
-
-</p>
-<p>Rsyslogd supports an enhanced syslog.conf file format, and also works
-with the standard syslog.conf. In theory, it should be possible to simply replace
-the syslogd binary with the one that comes with rsyslog. Of course, in order
-to use any of the new features, you must re-write your syslog.conf. To learn
-how to do this, please review our commented <a href="sample.conf.php">sample.conf</a>
-file. It outlines the enhancements over stock syslogd.
-<p>If you are interested in the <a href="http://en.wikipedia.org/wiki/IHE">IHE</a>
-environment, you might be interested to hear that rsyslog supports message with
-sizes of 32k and more. This feature has been tested, but by default is turned off
-(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 "IHE" - you
-will find easy and precise instructions on what you need to change (it's just
-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>
- <li><a href="http://www.rsyslog.com/Topic4.phtml">the rsyslog change log</a></li>
-</ul>
-</body>
+<html> +<head> +<title>rsyslog history</title> +</head> +<body> +<h1>RSyslog - History</h1> + +<b>Rsyslog is a GPL-ed, enhanced syslogd. Among others, it offers support for +reliable syslog over TCP, writing to +MySQL databases and fully configurable output formats (including great timestamps).</b> +Rsyslog was initiated by Rainer Gerhards. It has +been forked from the <a href="http://www.infodrom.org/projects/sysklogd/">sysklogd standard package</a>. +The goal of the +rsyslog project is to provide a more configurable and reliable +syslog deamon while retaining drop-in replacement capabilities for stock syslogd. By "reliable", we mean support for reliable transmission +modes like TCP or <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a> (syslog-reliable). +We do NOT imply that the sysklogd package is unreliable. In fact, the +opposite is the case and we assume that for the time being the well-used +sysklogd package offers better program reliability than our +brand-new modifications to it. + +</p><p>The name "rsyslog" stems back to the +planned support for syslog-reliable. Ironically, the initial release +of rsyslog did NEITHER support syslog-reliable NOR tcp based syslog. +Instead, it contains enhanced configurability and other enhancements +(like database support). The reason for this is that full support for +RFC 3195 would require even more changes and especially fundamental architectural +changes. Also, questions asked on the loganalysis list and at other +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, a bit later sending via TCP, too. Starting +with 1.11.0, RFC 3195 is finally support at the receiving side (a.k.a. "listener"). +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 +require at least one considerable architectural change to the syslogd +and this might delay things a little. Our immediate goal is to receive +feedback and get the bugs out of the current release. Only after that +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.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. + +</p> +<p>Rsyslogd supports an enhanced syslog.conf file format, and also works +with the standard syslog.conf. In theory, it should be possible to simply replace +the syslogd binary with the one that comes with rsyslog. Of course, in order +to use any of the new features, you must re-write your syslog.conf. To learn +how to do this, please review our commented <a href="sample.conf.php">sample.conf</a> +file. It outlines the enhancements over stock syslogd. +<p>If you are interested in the <a href="http://en.wikipedia.org/wiki/IHE">IHE</a> +environment, you might be interested to hear that rsyslog supports message with +sizes of 32k and more. This feature has been tested, but by default is turned off +(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 "IHE" - you +will find easy and precise instructions on what you need to change (it's just +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>In <b>June 2007</b>, Peter Vrabec from Red Hat helped us to create +RPM files for Fedora as well as supporting IPv6. There also seemed to be some +interest from the Red Hat community. This interest and new ideas resulted in a +very busy time with many great additions.<p>In <b>July 2007</b>, Andrew +Pantyukhin added BSD ports files for rsyslog and liblogging. We were strongly +encouraged by this too. It looks like rsyslog is getting more and more momentum. +Let's see what comes next...<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> + <li><a href="http://www.rsyslog.com/Topic4.phtml">the rsyslog change log</a></li> +</ul> +</body> </html>
\ No newline at end of file diff --git a/doc/rsyslog_packages.html b/doc/rsyslog_packages.html index 6bf03c5c..8cdd2e73 100644 --- a/doc/rsyslog_packages.html +++ b/doc/rsyslog_packages.html @@ -1,31 +1,37 @@ -<html>
-<head>
-<title>rsyslog precompiled packages (RPM and such...)</title>
-</head>
-<body>
-<h1>rsyslog packages</h1>
-<p><b>Thanks to some volunteers, rsyslog is also available in package form on
-some distributions.</b> All available packages are listed below. If you would
-like to maintain a package for a new distribution, please mail me at
-<a href="mailto:rgerhards@adiscon.com">rgerhards@adiscon.com</a>. Any help is *deeply*
-appreciated. While I create the core daemon, the package maintainers are really
-filling it with life, making it available to the average user. I am very
-grateful for that!</p>
-<p>This list has last been updated on 2006-09-26 by
-<a href="http://www.adiscon.com/en/people/rainer-gerhards.php">Rainer Gerhards</a>.
-New packages may appear at any time, so be sure to check this page whenever you
-need a new one.</p>
-<h2>CentOS 4.3</h2>
-<a href="http://www.se-community.com/~james/rsyslog/">
-http://www.se-community.com/~james/rsyslog/</a></p>
-<p>Maintained by<b> James Bergamin.</b></p>
-<h2>Almost any Linux</h2>
-<p><b>Bennet Todd</b> maintains packages that should work on almost any Linux.
-He keeps a current i386 tree. There is also a PPC tree, but that one is not paid
-much attention for (anyhow, it is known to typically work well, too).</p>
-<p>Please visit <a href="http://bent.latency.net/bent/">
-http://bent.latency.net/bent/</a>, select the relevant tree and then do a search
-for rsyslog.</p>
-
-</body>
-</html>
+<html> +<head> +<title>rsyslog precompiled packages (RPM and such...)</title> +</head> +<body> +<h1>rsyslog packages</h1> +<p><b>Thanks to some volunteers, rsyslog is also available in package form on +some distributions.</b> All available packages are listed below. If you would +like to maintain a package for a new distribution, please mail me at +<a href="mailto:rgerhards@adiscon.com">rgerhards@adiscon.com</a>. Any help is *deeply* +appreciated. While I create the core daemon, the package maintainers are really +filling it with life, making it available to the average user. I am very +grateful for that!</p> +<p>This list has last been updated on 2007-07-06 by +<a href="http://www.adiscon.com/en/people/rainer-gerhards.php">Rainer Gerhards</a>. +New packages may appear at any time, so be sure to check this page whenever you +need a new one.</p> +<p>Red Hat has recently begun to build RPMs for rsyslog. The URL changes, but a +good place to look for them is at +<a href="http://freshmeat.net/projects/rsyslog/">freshmeat's rsyslog info page</a>.</p> +<h2>BSD</h2> +<p>Give <a href="http://www.freshports.org/sysutils/rsyslog/"> +http://www.freshports.org/sysutils/rsyslog/</a> a try.</p> +<h2>CentOS 4.3</h2> +<a href="http://www.se-community.com/~james/rsyslog/"> +http://www.se-community.com/~james/rsyslog/</a></p> +<p>Maintained by<b> James Bergamin.</b></p> +<h2>Almost any Linux</h2> +<p><b>Bennet Todd</b> maintains packages that should work on almost any Linux. +He keeps a current i386 tree. There is also a PPC tree, but that one is not paid +much attention for (anyhow, it is known to typically work well, too).</p> +<p>Please visit <a href="http://bent.latency.net/bent/"> +http://bent.latency.net/bent/</a>, select the relevant tree and then do a search +for rsyslog.</p> + +</body> +</html> diff --git a/doc/status.html b/doc/status.html index f3deafbf..ade8da15 100644 --- a/doc/status.html +++ b/doc/status.html @@ -4,12 +4,12 @@ </head> <body> <h2>rsyslog status page</h2> -<p>This page reflects the status as of 2007-07-05.</p> +<p>This page reflects the status as of 2007-07-10.</p> <h2>Current Releases</h2> -<p><b>development:</b> 1.15.0 - <a href="http://www.rsyslog.com/Article83.phtml">change log</a> - -<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-38.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><b>development:</b> 1.15.1 - <a href="http://www.rsyslog.com/Article87.phtml">change log</a> - +<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-40.phtml">download</a></p> +<p><b>stable:</b> 1.0.5 - <a href="http://www.rsyslog.com/Article85.phtml">change log</a> - +<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-39.phtml">download</a></p> <p> (<a href="version_naming.html">How are versions named?</a>)</p> <p><font color="#FF0000"><b>Do NOT use versions prior to 1.10.1 or 1.0.1, because they contain a SQL injection vulnerability</b></font> (<a href="http://www.rsyslog.com/Article35.phtml">read @@ -546,26 +546,12 @@ The file containing the process id of .BR rsyslogd . .PD .SH BUGS -This is an early release of -.B Rsyslogd . -As such, there are probably a number of bugs. Those that I know -are described in the file BUGS that came with the package. Be sure -to review it. - -If an error occurs in one line the whole rule is ignored. - -.B Rsyslogd -doesn't change the filemode of opened logfiles at any stage of -process. If a file is created it is world readable. If you want to -avoid this, you have to create it and change permissions on your own. -This could be done in combination with rotating logfiles using the -.BR savelog (8) -program that is shipped in the -.B smail -3.x distribution. Remember that it might be a security hole if -everybody is able to read auth.* messages as these might contain -passwords. -.LP +Please review the file BUGS for up-to-date information on known +bugs and annouyances. +.SH Further Information +Please visit +.BR http://www.rsyslog.com/doc +for additional information, tutorials and a support forum. .SH SEE ALSO .BR rsyslog.conf (5), .BR logger (1), |