1kproplog(1M)            System Administration Commands            kproplog(1M)
2
3
4

NAME

6       kproplog - display the contents of the Kerberos principal update log
7

SYNOPSIS

9       /usr/sbin/kproplog [-h | -e num]
10
11

DESCRIPTION

13       The kproplog displays the contents of the Kerberos principal update log
14       to standard output. This command can be  used  to  keep  track  of  the
15       incremental  updates  to  the  principal  database, which is enabled by
16       default. The /var/krb5/principal.ulog  file  contains  the  update  log
17       maintained  by the kadmind(1M) process on the master KDC server and the
18       kpropd(1M) process on the slave KDC servers. When updates  occur,  they
19       are  logged  to  this  file.  Subsequently any KDC slave configured for
20       incremental updates will request the current data from the  master  KDC
21       and update their principal.ulog file with any updates returned.
22
23
24       The  kproplog  command  can only be run on a KDC server by someone with
25       privileges comparable to the superuser. It will display update  entries
26       for that server only.
27
28
29       If  no  options  are  specified,  the summary of the update log is dis‐
30       played. If invoked on the master, all of the update  entries  are  also
31       displayed.  When  invoked  on a slave KDC server, only a summary of the
32       updates are displayed, which includes the serial  number  of  the  last
33       update received and the associated time stamp of the last update.
34

OPTIONS

36       The following options are supported:
37
38       -h         Display  a  summary  of  the  update  log.  This information
39                  includes the database version number, state of the database,
40                  the  number  of  updates  in  the log, the time stamp of the
41                  first and last update, and the version number of  the  first
42                  and last update entry.
43
44
45       -e num     Display the last num update entries in the log. This is use‐
46                  ful when debugging synchronization between KDC servers.
47
48
49       -v         Display individual attributes per update. An example of  the
50                  output generated for one entry:
51
52                    Update Entry
53                        Update serial # : 4
54                        Update operation : Add
55                        Update principal : test@EXAMPLE.COM
56                        Update size : 424
57                        Update committed : True
58                        Update time stamp : Fri Feb 20 23:37:42 2004
59                        Attributes changed : 6
60                              Principal
61                              Key data
62                              Password last changed
63                              Modifying principal
64                              Modification time
65                              TL data
66
67
68

FILES

70       /var/krb5/principal.ulog    The  update log file for incremental propa‐
71                                   gation.
72
73

ATTRIBUTES

75       See attributes(5) for descriptions of the following attributes:
76
77
78
79
80       ┌─────────────────────────────┬─────────────────────────────┐
81       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
82       ├─────────────────────────────┼─────────────────────────────┤
83       │Availability                 │SUNWkdcu                     │
84       ├─────────────────────────────┼─────────────────────────────┤
85       │Interface Stability          │Evolving                     │
86       └─────────────────────────────┴─────────────────────────────┘
87

SEE ALSO

89       kpasswd(1),  gkadmin(1M),   kadmin(1M),   kadmind(1M),   kdb5_util(1M),
90       kprop(1M),  kpropd(1M),  kadm5.acl(4), kdc.conf(4), attributes(5), ker‐
91       beros(5)
92
93
94
95SunOS 5.11                        29 Mar 2004                     kproplog(1M)
Impressum