3
<title>Kerberos V5 System Administrator's Guide</title>
4
<meta http-equiv="Content-Type" content="text/html">
5
<meta name="description" content="Kerberos V5 System Administrator's Guide">
6
<meta name="generator" content="makeinfo 4.5">
7
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home">
12
Node:<a name="logging">logging</a>,
13
Next:<a rel="next" accesskey="n" href="capaths.html#capaths">capaths</a>,
14
Previous:<a rel="previous" accesskey="p" href="domain_realm.html#domain_realm">domain_realm</a>,
15
Up:<a rel="up" accesskey="u" href="krb5.conf.html#krb5.conf">krb5.conf</a>
19
<h4 class="subsection">[logging]</h4>
21
<p>The [logging] section indicates how a particular entity is to perform
22
its logging. The relations in this section assign one or more values to
23
the entity name. Currently, the following entities are used:
28
<dd>These entries specify how the KDC is to perform its logging.
30
<dt><b>admin_server</b>
31
<dd>These entries specify how the administrative server
32
is to perform its logging.
35
<dd>These entries specify how to perform logging in the
36
absence of explicit specifications otherwise.
39
<p>Values are of the following forms:
42
<dt><b>FILE=<filename></b>
44
<dt><b>FILE:<filename></b>
45
<dd>This value causes the entity's logging messages to go to the specified
46
file. If the <code>=</code> form is used, the file is overwritten. If the
47
<code>:</code> form is used, the file is appended to.
50
<dd>This value causes the entity's logging messages to go to its standard
54
<dd>This value causes the entity's logging messages to go to the console, if
55
the system supports it.
57
<dt><b>DEVICE=<devicename></b>
58
<dd>This causes the entity's logging messages to go to the specified device.
60
<dt><b>SYSLOG[:<severity>[:<facility>]]</b>
61
<dd>This causes the entity's logging messages to go to the system log.
63
<p>The <dfn>severity</dfn> argument specifies the default severity of system log
64
messages. This may be any of the following severities supported by the
65
<code>syslog(3)</code> call, minus the LOG_ prefix: LOG_EMERG, LOG_ALERT,
66
LOG_CRIT, LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO, and LOG_DEBUG.
67
For example, a value of <code>CRIT</code> would specify LOG_CRIT severity.
69
<p>The facility argument specifies the facility under which the messages
70
are logged. This may be any of the following facilities supported by
71
the syslog(3) call minus the LOG_ prefix: LOG_KERN, LOG_USER, LOG_MAIL,
72
LOG_DAEMON, LOG_AUTH, LOG_LPR, LOG_NEWS, LOG_UUCP, LOG_CRON, and
73
LOG_LOCAL0 through LOG_LOCAL7.
75
<p>If no severity is specified, the default is ERR. If no facility is
76
specified, the default is AUTH.
79
<p>In the following example, the logging messages from the KDC will go to
80
the console and to the system log under the facility LOG_DAEMON with
81
default severity of LOG_INFO; and the logging messages from the
82
administrative server will be appended to the file /var/adm/kadmin.log
83
and sent to the device /dev/tty04.
85
<pre class="smallexample"> [logging]
87
kdc = SYSLOG:INFO:DAEMON
88
admin_server = FILE:/var/adm/kadmin.log
89
admin_server = DEVICE=/dev/tty04