From 47ccbe9c67c0b3ca518449d80be387ca09904026 Mon Sep 17 00:00:00 2001 From: Michael Meckelein Date: Tue, 8 Jan 2008 12:58:38 +0000 Subject: modload info added (v3) --- doc/install.html | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'doc/install.html') diff --git a/doc/install.html b/doc/install.html index bee136ce..849c4ffe 100644 --- a/doc/install.html +++ b/doc/install.html @@ -53,7 +53,18 @@ the rsyslogd and the man pages to the relevant directories.

In this step, you tell rsyslogd what to do with received messages. If you are upgrading from stock syslogd, /etc/syslog.conf is probably a good starting point. Rsyslogd understands stock syslogd syntax, so you can simply copy over -/etc/syslog.conf to /etc/rsyslog.conf. Then, edit rsyslog.conf for any +/etc/syslog.conf to /etc/rsyslog.conf. Note since version 3 rsyslog requires +to load plug-in modules to perform useful work (more about +compatibilty notes v3). To load the most common plug-ins, +add the following to the top of rsyslog.conf:

+

+$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) +

+Change rsyslog.conf for any further enhancements you would like to see. For example, you can add database writing as outlined in the paper "Writing syslog Data to MySQL" (remember you need to enable MySQL support during step 2 if you want to do -- cgit