mirror of
https://github.com/rsyslog/rsyslog.git
synced 2025-12-19 19:40:41 +01:00
doc updates for release 1.14.0
This commit is contained in:
Rainer Gerhards
parent
56c8bd7bde
commit
2a98edf43b
108
doc/bugs.html
108
doc/bugs.html
@ -1,54 +1,54 @@
|
||||
<html>
|
||||
<head>
|
||||
<title>rsyslog bugs and annoyances</title>
|
||||
</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. 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
|
||||
<a href="http://www.adiscon.com/en/people/rainer-gerhards.php">Rainer Gerhards</a>.</p>
|
||||
<h1>rsyslogd</h1>
|
||||
<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
|
||||
template definition. I also strongly doubt I will ever support this, because
|
||||
it does not make an awful lot of sense (after all, why not use two template
|
||||
names...).</p>
|
||||
<h2>MEMORY LEAK ON HUPING</h2>
|
||||
<p>Currently, the template memory is NOT freed when SIGHUP is received.
|
||||
This causes a small memory leak on each HUP. Will be fixed soon and
|
||||
should not cause real trouble unless you HUP syslogd quite frequently.</p>
|
||||
<h2>WALLMSG FORMAT (* selector)
|
||||
</h2>
|
||||
<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
|
||||
instances does not work. Use TCP instead.</p>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
<html>
|
||||
<head>
|
||||
<title>rsyslog bugs and annoyances</title>
|
||||
</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-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>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
|
||||
template definition. I also strongly doubt I will ever support this, because
|
||||
it does not make an awful lot of sense (after all, why not use two template
|
||||
names...).</p>
|
||||
<h2>MEMORY LEAK ON HUPING</h2>
|
||||
<p>Currently, the template memory is NOT freed when SIGHUP is received.
|
||||
This causes a small memory leak on each HUP. Will be fixed soon and
|
||||
should not cause real trouble unless you HUP syslogd quite frequently.</p>
|
||||
<h2>WALLMSG FORMAT (* selector)
|
||||
</h2>
|
||||
<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
|
||||
instances does not work. Use TCP instead.</p>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,47 +1,50 @@
|
||||
<html>
|
||||
<head>
|
||||
<title>rsyslog features</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>RSyslog - Features</h1>
|
||||
<p><b>This page lists both current features as well as those being considered
|
||||
for future versions of rsyslog.</b> If you think a feature is missing, drop
|
||||
<a href="mailto:rgerhards@adiscon.com">Rainer</a> a note. Rsyslog is a vital
|
||||
project. Features are added each few days. If you would like to keep up of what
|
||||
is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mailman/listinfo/rsyslog">rsyslog mailing list</a>.
|
||||
</p>
|
||||
<h2>Current Features</h2>
|
||||
<ul>
|
||||
|
||||
<li>native support for <a href="rsyslog_mysql.html">writing to MySQL databases</a><li>support for (plain) tcp
|
||||
based syslog - much better reliability<li>support for sending and receiving
|
||||
compressed syslog messages<li>support for receiving messages via
reliable <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">
RFC 3195</a> delivery<li>control of log output format,
|
||||
including ability to present channel and priority as visible log data<li>good timestamp format control; at a minimum, ISO 8601/RFC 3339
|
||||
second-resolution UTC zone<li>ability to reformat message contents and work with substrings<li>support for
|
||||
log files larger than 2gb<li>support for file size limitation and automatic
|
||||
rollover command execution<li>support for running multiple rsyslogd
|
||||
instances on a single machine<li>support for <a href="rsyslog_stunnel.html">
|
||||
ssl-protected syslog</a> (via stunnel)<li>ability to filter on any part of
|
||||
the message, not just facility and severity<li>support for discarding
|
||||
messages based on filters<li>ability to execute shell scripts on received
|
||||
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>
|
||||
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>
|
||||
<p> </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) - simple regex already
|
||||
partly added. So far, this seems sufficient so that there is no urgent</ul>
|
||||
<p> </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>
|
||||
</body>
|
||||
</html>
|
||||
<html>
|
||||
<head>
|
||||
<title>rsyslog features</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>RSyslog - Features</h1>
|
||||
<p><b>This page lists both current features as well as those being considered
|
||||
for future versions of rsyslog.</b> If you think a feature is missing, drop
|
||||
<a href="mailto:rgerhards@adiscon.com">Rainer</a> a note. Rsyslog is a vital
|
||||
project. Features are added each few days. If you would like to keep up of what
|
||||
is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mailman/listinfo/rsyslog">rsyslog mailing list</a>.
|
||||
</p>
|
||||
<h2>Current Features</h2>
|
||||
<ul>
|
||||
|
||||
<li>native support for <a href="rsyslog_mysql.html">writing to MySQL databases</a><li>support for (plain) tcp
|
||||
based syslog - much better reliability<li>support for sending and receiving
|
||||
compressed syslog messages<li>support for receiving messages via
reliable <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">
RFC 3195</a> delivery<li>control of log output format,
|
||||
including ability to present channel and priority as visible log data<li>good timestamp format control; at a minimum, ISO 8601/RFC 3339
|
||||
second-resolution UTC zone<li>ability to reformat message contents and work with substrings<li>support for
|
||||
log files larger than 2gb<li>support for file size limitation and automatic
|
||||
rollover command execution<li>support for running multiple rsyslogd
|
||||
instances on a single machine<li>support for <a href="rsyslog_stunnel.html">
|
||||
ssl-protected syslog</a> (via stunnel)<li>ability to filter on any part of
|
||||
the message, not just facility and severity<li>support for discarding
|
||||
messages based on filters<li>ability to execute shell scripts on received
|
||||
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<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<li>
|
||||
support for IPv6 (currently UDP only, but TCP will be added soon)</ul>
|
||||
<p> </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>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,
|
||||
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>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -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> (<a href="version_naming.html">How are versions named?</a>)</p>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user