From 328056cfab448bf305238cffe48862beee0a2a87 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards
With v2 and below, inputs were automatically started together with rsyslog. +In v3, inputs are optional! They come in the form of plug-in modules. +At least one input module must be loaded to make +rsyslog do any useful work. The config file directives doc briefly +lists which config statements are available by which modules.
+It is suggested that input modules be loaded in the top part of the config +file. Here is an example, also highlighting the most important modules:
+$ModLoad immark # provides --MARK-- message capability
+$ModLoad imudp # provides UDP syslog reception
+$ModLoad imtcp # provides TCP syslog reception and GSS-API (if compiled to
+support it)
+$ModLoad imuxsock # provides support for local system logging (e.g. via logger
+command)
+$ModLoad imklog # provides kernel logging support (previously done by rklogd)
A number of command line options have been removed. New config file directives have been added for them. Once we implement compatibiltiy mode, these @@ -59,6 +74,10 @@ 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
Either "FixedArray" or "LinkedList" is recommended. "Direct" is available, +but should not be used except for a very good reason ("Direct" disables queueing +and will potentially lead to message loss on the input side).
I have decided to move the todo list for v3 also into this document. After all, it is kind of a compatibility issue ;) But, more seriously, I think this is -- cgit v1.2.3