Current Path: > > lib > dracut > modules.d > 98syslog
Operation : Linux premium88.web-hosting.com 4.18.0-553.54.1.lve.el8.x86_64 #1 SMP Wed Jun 4 13:01:13 UTC 2025 x86_64 Software : Apache Server IP : 185.61.154.216 | Your IP: 216.73.216.44 Domains : 1034 Domain(s) Permission : [ 0755 ]
Name | Type | Size | Last Modified | Actions |
---|---|---|---|---|
README | File | 833 bytes | July 15 2025 09:09:22. | |
module-setup.sh | File | 1169 bytes | July 15 2025 09:09:22. | |
parse-syslog-opts.sh | File | 1154 bytes | October 08 2018 13:38:33. | |
rsyslog.conf | File | 820 bytes | October 08 2018 13:38:33. | |
rsyslogd-start.sh | File | 1233 bytes | October 08 2018 13:38:33. | |
rsyslogd-stop.sh | File | 286 bytes | October 08 2018 13:38:33. | |
syslog-cleanup.sh | File | 407 bytes | October 08 2018 13:38:33. |
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 appropriate 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
SILENT KILLER Tool