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
|
<html lang="en">
<head>
<title>Kerberos V5 System Administrator's Guide</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Kerberos V5 System Administrator's Guide">
<meta name="generator" content="makeinfo 4.5">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home">
</head>
<body>
<div class="node">
<p>
Node:<a name="logging">logging</a>,
Next:<a rel="next" accesskey="n" href="capaths.html#capaths">capaths</a>,
Previous:<a rel="previous" accesskey="p" href="domain_realm.html#domain_realm">domain_realm</a>,
Up:<a rel="up" accesskey="u" href="krb5.conf.html#krb5.conf">krb5.conf</a>
<hr><br>
</div>
<h4 class="subsection">[logging]</h4>
<p>The [logging] section indicates how a particular entity is to perform
its logging. The relations in this section assign one or more values to
the entity name. Currently, the following entities are used:
<dl>
<dt><b>kdc</b>
<dd>These entries specify how the KDC is to perform its logging.
<dt><b>admin_server</b>
<dd>These entries specify how the administrative server
is to perform its logging.
<dt><b>default</b>
<dd>These entries specify how to perform logging in the
absence of explicit specifications otherwise.
</dl>
<p>Values are of the following forms:
<dl>
<dt><b>FILE=<filename></b>
<dd>
<dt><b>FILE:<filename></b>
<dd>This value causes the entity's logging messages to go to the specified
file. If the <code>=</code> form is used, the file is overwritten. If the
<code>:</code> form is used, the file is appended to.
<dt><b>STDERR</b>
<dd>This value causes the entity's logging messages to go to its standard
error stream.
<dt><b>CONSOLE</b>
<dd>This value causes the entity's logging messages to go to the console, if
the system supports it.
<dt><b>DEVICE=<devicename></b>
<dd>This causes the entity's logging messages to go to the specified device.
<dt><b>SYSLOG[:<severity>[:<facility>]]</b>
<dd>This causes the entity's logging messages to go to the system log.
<p>The <dfn>severity</dfn> argument specifies the default severity of system log
messages. This may be any of the following severities supported by the
<code>syslog(3)</code> call, minus the LOG_ prefix: LOG_EMERG, LOG_ALERT,
LOG_CRIT, LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO, and LOG_DEBUG.
For example, a value of <code>CRIT</code> would specify LOG_CRIT severity.
<p>The facility argument specifies the facility under which the messages
are logged. This may be any of the following facilities supported by
the syslog(3) call minus the LOG_ prefix: LOG_KERN, LOG_USER, LOG_MAIL,
LOG_DAEMON, LOG_AUTH, LOG_LPR, LOG_NEWS, LOG_UUCP, LOG_CRON, and
LOG_LOCAL0 through LOG_LOCAL7.
<p>If no severity is specified, the default is ERR. If no facility is
specified, the default is AUTH.
</dl>
<p>In the following example, the logging messages from the KDC will go to
the console and to the system log under the facility LOG_DAEMON with
default severity of LOG_INFO; and the logging messages from the
administrative server will be appended to the file /var/adm/kadmin.log
and sent to the device /dev/tty04.
<pre class="smallexample"> [logging]
kdc = CONSOLE
kdc = SYSLOG:INFO:DAEMON
admin_server = FILE:/var/adm/kadmin.log
admin_server = DEVICE=/dev/tty04
</pre>
</body></html>
|
