blob: 409021b754000a352923e00cd77f7935efe0e5c7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
<?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">
<title>Sysklogd-&sysklogd-version;</title>
<?dbhtml filename="sysklogd.html"?>
<indexterm zone="ch-system-sysklogd"><primary sortas="a-Sysklogd">Sysklogd</primary></indexterm>
<para>The Sysklogd package contains programs for logging system messages, such
as those given by the kernel when unusual things happen.</para>
<screen>&buildtime; 0.1 SBU
&diskspace; 0.5 MB</screen>
<para>Sysklogd installation depends on: Binutils, Coreutils, GCC, Glibc, Make.</para>
<sect2>
<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"><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"</userinput>
# 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
<userinput>EOF</userinput></screen>
</sect2>
<sect2 id="contents-sysklogd"><title>Contents of Sysklogd</title>
<para><emphasis>Installed programs</emphasis>: klogd and syslogd</para>
</sect2>
<sect2><title>Short descriptions</title>
<indexterm zone="ch-system-sysklogd klogd"><primary sortas="b-klogd">klogd</primary></indexterm>
<para id="klogd"><command>klogd</command> is a system daemon for intercepting and
logging kernel messages.</para>
<indexterm zone="ch-system-sysklogd syslogd"><primary sortas="b-syslogd">syslogd</primary></indexterm>
<para id="syslogd"><command>syslogd</command> 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>
</sect2>
</sect1>
|
