HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man4/!!!intro.4
________________________________________________________________
___ ___
k
krb5.conf(4) krb5.conf(4)
default_domain
This relation identifies the default domain for the hosts in the realm. This is needed for
translating V4 principal names (which do not contain a domain name) to V5 principal
names (which do contain a domain name).
v4_instance_convert
This subsection allows the administrator to configure exceptions to the default_domain
mapping rule. It contains V4 instances (the tag name) which should be translated to some
specific hostname (the tag value) similar to the second component in a Kerberos V5 princi-
pal name.
domain_realm Section
The [domain_realm] section provides a translation from a hostname to the Kerberos realm name for
the services provided by that host.
The tag name can be a hostname or a domain name, where domain names are indicated by a prefix of a
period (’.’) character. The value of the relation is the Kerberos realm name for that particular host or
domain. Host names and domain names should be in lower case.
If no translation entry applies, the host’s realm is considered to be the hostname’s domain portion con-
verted to upper case. For example, the following
[domain_realm] section:
[domain_realm]
.mit.edu = ATHENA.MIT.EDU
mit.edu = ATHENA.MIT.EDU
dodo.mit.edu = SMS_TEST.MIT.EDU
.ucsc.edu = CATS.UCSC.EDU
maps dodo.mit.edu into the SMS_TEST.MIT.EDU realm. All other hosts in the MIT.EDU domain to the
ATHENA.MIT.EDU realm, and all hosts in the UCSC.EDU domain into the CATS.UCSC.EDU realm.
ucbvax.berkeley.edu would be mapped by the default rules to the BERKELEY.EDU realm.
sage.lcs.mit.edu would be mapped to the LCS.MIT.EDU realm.
logging Section
The
[logging] section indicates how a particular entity is to perform its logging. The relations specified
in this section assign one or more values to the entity name.
Currently, the following entities are used:
kdc These entries specify how the Key DistributionCenter is to perform its logging.
admin_server
These entries specify how the administrative server is to perform its logging.
default These entries specify how to perform logging in the absence of explicit specifications other-
wise.
Values are of the following forms:
FILE=filename
FILE:filename
This value causes the entity’s logging messages to go to the specified file. If the
= form is
used, then the file is overwritten. Otherwise, the file is appended to.
STDERR This value causes the entity’s logging messages to go to its standard error stream.
CONSOLE This value causes the entity’s logging messages to go to the console if the system supports
it.
DEVICE=devicename
This causes the entity’s logging messages to go to the specified device.
SYSLOG[:severity[:facility]]
This causes the entity’s logging messages to go to the system log.
The severity argument specifies the default severity of system log messages. This may be any of the follow-
ing severities mentioned below supported by the syslog() call (see the syslog(3C) manual page). The
supported arguments are:
LOG_ALERT LOG_CRIT LOG_DEBUG LOG_ERR
Section 4−−148 − 3 − HP-UX Release 11i: December 2000
___
___