1 Start the Kerberos daemons on the master KDC
2 ===============================================
4 At this point, you are ready to start the Kerberos KDC
5 (:ref:`krb5kdc(8)`) and administrative daemons on the Master KDC. To
8 shell% /usr/local/sbin/krb5kdc
9 shell% /usr/local/sbin/kadmind
11 Each server daemon will fork and run in the background.
13 .. note:: Assuming you want these daemons to start up automatically at
14 boot time, you can add them to the KDC's ``/etc/rc`` or
15 ``/etc/inittab`` file. You need to have a
16 :ref:`stash_definition` in order to do this.
18 You can verify that they started properly by checking for their
19 startup messages in the logging locations you defined in
20 krb5.conf. (See :ref:`logging`). For example::
22 shell% tail /var/log/krb5kdc.log
23 Dec 02 12:35:47 beeblebrox krb5kdc[3187](info): commencing operation
24 shell% tail /var/log/kadmin.log
25 Dec 02 12:35:52 beeblebrox kadmind[3189](info): starting
27 Any errors the daemons encounter while starting will also be listed in
30 As an additional verification, check if kinit succeeds against the
31 principals that you have created on the previous step
32 (:ref:`addadmin_kdb`). Run::
34 shell% /usr/local/bin/kinit admin/admin@ATHENA.MIT.EDU
36 You are now ready to start configuring the slave KDCs.
38 .. note:: Assuming you are setting the KDCs up so that you can easily
39 switch the master KDC with one of the slaves, you should
40 perform each of these steps on the master KDC as well as the
41 slave KDCs, unless these instructions specify otherwise.
47 Please, provide your feedback or suggest a new topic at
48 krb5-bugs@mit.edu?subject=Documentation___install_kdc