3
.\" Copyright 2008 by the Massachusetts Institute of Technology.
5
.\" Export of this software from the United States of America may
6
.\" require a specific license from the United States Government.
7
.\" It is the responsibility of any person or organization contemplating
8
.\" export to obtain such a license before exporting.
10
.\" WITHIN THAT CONSTRAINT, permission to use, copy, modify, and
11
.\" distribute this software and its documentation for any purpose and
12
.\" without fee is hereby granted, provided that the above copyright
13
.\" notice appear in all copies and that both that copyright notice and
14
.\" this permission notice appear in supporting documentation, and that
15
.\" the name of M.I.T. not be used in advertising or publicity pertaining
16
.\" to distribution of the software without specific, written prior
17
.\" permission. Furthermore if you modify this software you must label
18
.\" your software as modified software and not distribute it in such a
19
.\" fashion that it might be confused with the original M.I.T. software.
20
.\" M.I.T. makes no representations about the suitability of
21
.\" this software for any purpose. It is provided "as is" without express
22
.\" or implied warranty.
25
.\" Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved
29
kproplog \- display the contents of the Kerberos principal update log
32
[\fB\-h\fP] [\fB\-e\fP \fInum\fP]
37
command displays the contents of the Kerberos principal update log to
38
standard output. It can be used to keep track of the incremental
39
updates to the principal database, when enabled. The update log
40
file contains the update log maintained by the
42
process on the master KDC server and the kpropd process on the slave
43
KDC servers. When updates occur, they are logged to this
44
file. Subsequently any KDC slave configured for incremental updates
45
will request the current data from the master KDC and update their
47
file with any updates returned.
51
command can only be run on a KDC server by someone with privileges
52
comparable to the superuser. It will display update entries for that
55
If no options are specified, the summary of the update log is
56
displayed. If invoked on the master, all of the update entries are
57
also displayed. When invoked on a slave KDC server, only a summary of
58
the updates are displayed, which includes the serial number of the
59
last update received and the associated time stamp of the last update.
64
Display a summary of the update log. This information includes the
65
database version number, state of the database, the number of updates
66
in the log, the time stamp of the first and last update, and the
67
version number of the first and last update entry.
72
update entries in the log. This is useful when debugging
73
synchronization between KDC servers.
76
Display individual attributes per update.
77
An example of the output generated for one entry:
81
Update operation : Add
82
Update principal : test@EXAMPLE.COM
84
Update committed : True
85
Update time stamp : Fri Feb 20 23:37:42 2004
86
Attributes changed : 6