| 1 |
.. _kproplog(8): |
| 2 |
|
| 3 |
kproplog |
| 4 |
======== |
| 5 |
|
| 6 |
SYNOPSIS |
| 7 |
-------- |
| 8 |
|
| 9 |
**kproplog** [**-h**] [**-e** *num*] [-v] |
| 10 |
**kproplog** [-R] |
| 11 |
|
| 12 |
|
| 13 |
DESCRIPTION |
| 14 |
----------- |
| 15 |
|
| 16 |
The kproplog command displays the contents of the KDC database update |
| 17 |
log to standard output. It can be used to keep track of incremental |
| 18 |
updates to the principal database. The update log file contains the |
| 19 |
update log maintained by the :ref:`kadmind(8)` process on the primary |
| 20 |
KDC server and the :ref:`kpropd(8)` process on the replica KDC |
| 21 |
servers. When updates occur, they are logged to this file. |
| 22 |
Subsequently any KDC replica configured for incremental updates will |
| 23 |
request the current data from the primary KDC and update their log |
| 24 |
file with any updates returned. |
| 25 |
|
| 26 |
The kproplog command requires read access to the update log file. It |
| 27 |
will display update entries only for the KDC it runs on. |
| 28 |
|
| 29 |
If no options are specified, kproplog displays a summary of the update |
| 30 |
log. If invoked on the primary, kproplog also displays all of the |
| 31 |
update entries. If invoked on a replica KDC server, kproplog displays |
| 32 |
only a summary of the updates, which includes the serial number of the |
| 33 |
last update received and the associated time stamp of the last update. |
| 34 |
|
| 35 |
|
| 36 |
OPTIONS |
| 37 |
------- |
| 38 |
|
| 39 |
**-R** |
| 40 |
Reset the update log. This forces full resynchronization. If |
| 41 |
used on a replica then that replica will request a full resync. |
| 42 |
If used on the primary then all replicas will request full |
| 43 |
resyncs. |
| 44 |
|
| 45 |
**-h** |
| 46 |
Display a summary of the update log. This information includes |
| 47 |
the database version number, state of the database, the number of |
| 48 |
updates in the log, the time stamp of the first and last update, |
| 49 |
and the version number of the first and last update entry. |
| 50 |
|
| 51 |
**-e** *num* |
| 52 |
Display the last *num* update entries in the log. This is useful |
| 53 |
when debugging synchronization between KDC servers. |
| 54 |
|
| 55 |
**-v** |
| 56 |
Display individual attributes per update. An example of the |
| 57 |
output generated for one entry:: |
| 58 |
|
| 59 |
Update Entry |
| 60 |
Update serial # : 4 |
| 61 |
Update operation : Add |
| 62 |
Update principal : [email protected] |
| 63 |
Update size : 424 |
| 64 |
Update committed : True |
| 65 |
Update time stamp : Fri Feb 20 23:37:42 2004 |
| 66 |
Attributes changed : 6 |
| 67 |
Principal |
| 68 |
Key data |
| 69 |
Password last changed |
| 70 |
Modifying principal |
| 71 |
Modification time |
| 72 |
TL data |
| 73 |
|
| 74 |
|
| 75 |
ENVIRONMENT |
| 76 |
----------- |
| 77 |
|
| 78 |
See :ref:`kerberos(7)` for a description of Kerberos environment |
| 79 |
variables. |
| 80 |
|
| 81 |
|
| 82 |
SEE ALSO |
| 83 |
-------- |
| 84 |
|
| 85 |
:ref:`kpropd(8)`, :ref:`kerberos(7)` |