|
@@ -0,0 +1,111 @@
|
|
|
+<?xml version="1.0" encoding="ISO-8859-1"?>
|
|
|
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
|
|
|
+ <!ENTITY % general-entities SYSTEM "../general.ent">
|
|
|
+ %general-entities;
|
|
|
+]>
|
|
|
+<sect1 id="ch-system-sysklogd" xreflabel="Sysklogd" role="wrap">
|
|
|
+<title>Sysklogd-&sysklogd-version;</title>
|
|
|
+<?dbhtml filename="sysklogd.html"?>
|
|
|
+
|
|
|
+<indexterm zone="ch-system-sysklogd"><primary sortas="a-Sysklogd">Sysklogd</primary></indexterm>
|
|
|
+
|
|
|
+<sect2 role="package"><title/>
|
|
|
+<para>The Sysklogd package contains programs for logging system messages, such
|
|
|
+as those given by the kernel when unusual things happen.</para>
|
|
|
+
|
|
|
+<segmentedlist>
|
|
|
+<segtitle>&buildtime;</segtitle>
|
|
|
+<segtitle>&diskspace;</segtitle>
|
|
|
+<seglistitem><seg>0.1 SBU</seg><seg>0.5 MB</seg></seglistitem>
|
|
|
+</segmentedlist>
|
|
|
+
|
|
|
+<segmentedlist>
|
|
|
+<segtitle>Sysklogd installation depends on</segtitle>
|
|
|
+<seglistitem><seg>Binutils, Coreutils, GCC, Glibc, Make</seg></seglistitem>
|
|
|
+</segmentedlist>
|
|
|
+</sect2>
|
|
|
+
|
|
|
+<sect2 role="installation">
|
|
|
+<title>Installation of Sysklogd</title>
|
|
|
+
|
|
|
+<para>Sysklogd has issues with the Linux 2.6 kernel series - fix these isues
|
|
|
+by applying the following patch:</para>
|
|
|
+
|
|
|
+<screen><userinput>patch -Np1 -i ../sysklogd-&sysklogd-version;-kernel_headers-1.patch</userinput></screen>
|
|
|
+
|
|
|
+<para>There is also a race condition in the signal handling logic, and this
|
|
|
+sometimes confuses the <command>sysklogd</command> initscript.
|
|
|
+Fix this bug by applying another patch:</para>
|
|
|
+
|
|
|
+<screen><userinput>patch -Np1 -i ../sysklogd-&sysklogd-version;-signal-1.patch</userinput></screen>
|
|
|
+
|
|
|
+<para>Compile Sysklogd:</para>
|
|
|
+
|
|
|
+<screen><userinput>make</userinput></screen>
|
|
|
+
|
|
|
+<para>Now install it:</para>
|
|
|
+
|
|
|
+<screen><userinput>make install</userinput></screen>
|
|
|
+
|
|
|
+</sect2>
|
|
|
+
|
|
|
+
|
|
|
+<sect2 id="conf-sysklogd" role="configuration"><title>Configuring Sysklogd</title>
|
|
|
+<indexterm zone="conf-sysklogd">
|
|
|
+<primary sortas="a-Sysklogd">Sysklogd</primary>
|
|
|
+<secondary>configuring</secondary></indexterm>
|
|
|
+
|
|
|
+<indexterm zone="conf-sysklogd"><primary sortas="e-/etc/syslog.conf">/etc/syslog.conf</primary></indexterm>
|
|
|
+
|
|
|
+<para>Create a new <filename>/etc/syslog.conf</filename> file by running the
|
|
|
+following:</para>
|
|
|
+
|
|
|
+<screen><userinput>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
|
|
|
+*.emerg *
|
|
|
+
|
|
|
+# End /etc/syslog.conf
|
|
|
+EOF</userinput></screen>
|
|
|
+
|
|
|
+</sect2>
|
|
|
+
|
|
|
+
|
|
|
+<sect2 id="contents-sysklogd" role="content"><title>Contents of Sysklogd</title>
|
|
|
+
|
|
|
+<segmentedlist>
|
|
|
+<segtitle>Installed programs</segtitle>
|
|
|
+<seglistitem><seg>klogd and syslogd</seg></seglistitem>
|
|
|
+</segmentedlist>
|
|
|
+
|
|
|
+<variablelist><title>Short descriptions</title>
|
|
|
+
|
|
|
+<varlistentry id="klogd">
|
|
|
+<term><command>klogd</command></term>
|
|
|
+<listitem>
|
|
|
+<indexterm zone="ch-system-sysklogd klogd"><primary sortas="b-klogd">klogd</primary></indexterm>
|
|
|
+<para>is a system daemon for intercepting and logging kernel messages.</para>
|
|
|
+</listitem>
|
|
|
+</varlistentry>
|
|
|
+
|
|
|
+<varlistentry id="syslogd">
|
|
|
+<term><command>syslogd</command></term>
|
|
|
+<listitem>
|
|
|
+<indexterm zone="ch-system-sysklogd syslogd"><primary sortas="b-syslogd">syslogd</primary></indexterm>
|
|
|
+<para>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.</para>
|
|
|
+</listitem>
|
|
|
+</varlistentry>
|
|
|
+</variablelist>
|
|
|
+
|
|
|
+</sect2>
|
|
|
+
|
|
|
+</sect1>
|