dracut

History

Harald Hoyer c9f1e3d1f4 check for getarg() function before sourcing dracut-lib.sh make use of "type getarg" to check, if we really need to source dracut-lib.sh		2011-03-25 16:10:46 +01:00
..
README	Syslog support for dracut	2009-08-19 10:40:02 +02:00
module-setup.sh	syslog: fixed warn() and dwarning() calls	2011-03-15 19:51:07 +01:00
parse-syslog-opts.sh	check for getarg() function before sourcing dracut-lib.sh	2011-03-25 16:10:46 +01:00
rsyslog.conf	Syslog support for dracut	2009-08-19 10:40:02 +02:00
rsyslogd-start.sh	check for getarg() function before sourcing dracut-lib.sh	2011-03-25 16:10:46 +01:00
rsyslogd-stop.sh	reformat source code	2010-09-10 15:34:36 +02:00
syslog-cleanup.sh	check for getarg() function before sourcing dracut-lib.sh	2011-03-25 16:10:46 +01:00
syslog-genrules.sh	check for getarg() function before sourcing dracut-lib.sh	2011-03-25 16:10:46 +01:00

README

Syslog support for dracut

This module provides syslog functionality in the initrd.
This is especially interesting when complex configuration being 
used to provide access to the device the rootfs resides on.

When this module is installed into the ramfs it is triggered by 
the udev event from the nic being setup (online).

Then if syslog is configured it is started and will forward all
kernel messages to the given syslog server.

The syslog implementation is detected automatically by finding the 
apropriate binary with the following order:
rsyslogd
syslogd
syslog-ng
Then if detected the syslog.conf is generated and syslog is started.

Bootparameters:
syslogserver=ip    Where to syslog to
sysloglevel=level  What level has to be logged
syslogtype=rsyslog|syslog|syslogng  
                   Don't auto detect syslog but set it