From 01265220ceede40048b87fa2a561073ed8642d3a Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Mon, 17 Dec 2007 14:48:16 +0000 Subject: rsyslog v3 compatibility info --- doc/v3compatibility.html | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 doc/v3compatibility.html diff --git a/doc/v3compatibility.html b/doc/v3compatibility.html new file mode 100644 index 00000000..7c372162 --- /dev/null +++ b/doc/v3compatibility.html @@ -0,0 +1,32 @@ + +Writing syslog Data to MySQL + + + +

Compatibility notes for rsyslog v3

+

Written by + Rainer + Gerhards (2007-12-17)

+

Rsyslog aims to be a drop-in replacement for sysklogd. However, version 3 has +some considerable enhancements, which lead to some backward compatibility issues +both in regard to sysklogd and rsyslog v1 and v2.

+

Rsyslog v3 is currently under initial development. Compatibility issues may +be resolved, so be sure to check back often. Also, comments and suggestions are +appreciated. Feedback right in time can now have a big impact on the route we +take ;)

+

-m command line option

+

The -m command line option is ignored for the time being. There is no default +mark period. If you need a 20 minute mark period you need to

+

$ModLoad immark # wherever this is
+$MarkMessageInterval 1800 # 20 minutes

+

klogd

+

klogd has (finally) been replaced by a loadable input module. To enable klogd +functionality, do

+

$ModLoad imklog

+

A limited set of klogd command line settings is now supported via +rsyslog.conf. That set of configuration directives is to be expanded. So far, we +support:

+

$klogSymbolsTwice [on/off]
+$DebugPrintKernelSymbols [on/off] # spits *a lot* of messages at startup

+ + -- cgit v1.2.3