Sysklogd: Difference between revisions
From CBLFS
Jump to navigationJump to search
New page: {| style="text-align: left; background-color: AliceBlue;" |- !Download Source: | http:http://www.infodrom.org/projects/sysklogd/download/sysklogd-{{Sysklogd-Version}}.tar.gz |} ---- {{Pa... |
No edit summary |
||
| Line 53: | Line 53: | ||
# End /etc/syslog.conf | # End /etc/syslog.conf | ||
EOF | EOF | ||
=== BootScript === | |||
Install the init script included in the [[bootscripts]] package. | |||
make install-sysklogd | |||
== Contents == | == Contents == | ||
Revision as of 09:58, 31 January 2009
| Download Source: | http:http://www.infodrom.org/projects/sysklogd/download/sysklogd-1.5.tar.gz |
|---|
Introduction to Sysklogd
The Sysklogd package contains programs for logging system messages, such as those given by the kernel when unusual things happen
Project Homepage: http://www.infodrom.org/projects/sysklogd
Non-Multilib
Compile the package:
make
Install the package:
make install
Multilib
This package does not provide any libraries so only one installation is required.
make CC="gcc ${BUILD64}"
Install the package:
make install
Configuring Sysklogd
Create a new /etc/syslog.conf file by running the following:
cat > /etc/syslog.conf << "EOF"
# Begin /etc/syslog.conf
auth,authpriv.* -/var/log/auth.log
*.*;auth,authpriv.none -/var/log/sys.log
daemon.* -/var/log/daemon.log
kern.* -/var/log/kern.log
mail.* -/var/log/mail.log
user.* -/var/log/user.log
*.info;mail.none;authpriv.none;cron.none -/var/log/messages
*.emerg *
# log the bootscript output:
local2.* -/var/log/boot.log
# End /etc/syslog.conf
EOF
BootScript
Install the init script included in the bootscripts package.
make install-sysklogd
Contents
| Installed Directories: | /usr/sbin |
|---|---|
| Installed Programs: | klogd and syslogd |
| Installed Libraries: | none |
Short Descriptions
| klogd | A system daemon for intercepting and logging kernel messages |
|---|---|
| syslogd | Logs the messages that system programs offer for logging. Every logged message contains at least a date stamp and a hostname, and normally the program's name too, but that depends on how trusting the logging daemon is told to be. |