1IPROP(8) BSD System Manager's Manual IPROP(8)
2
4 iprop, ipropd-master, ipropd-slave — propagate transactions from a Heim‐
5 dal Kerberos master KDC to slave KDCs
6
8 ipropd-master [-c string | --config-file=string] [-r string |
9 --realm=string] [-k kspec | --keytab=kspec] [-d file |
10 --database=file] [--slave-stats-file=file]
11 [--time-missing=time] [--time-gone=time] [--detach]
12 [--version] [--help]
13 ipropd-slave [-c string | --config-file=string] [-r string |
14 --realm=string] [-k kspec | --keytab=kspec]
15 [--time-lost=time] [--detach] [--version] [--help] master
16
18 ipropd-master is used to propagate changes to a Heimdal Kerberos database
19 from the master Kerberos server on which it runs to slave Kerberos
20 servers running ipropd-slave.
21 The slaves are specified by the contents of the slaves file in the KDC's
23 database directory, e.g. /var/heimdal/slaves. This has principals one
24 per-line of the form
25 iprop/slave@REALM
26 where slave is the hostname of the slave server in the given REALM, e.g.
27 iprop/kerberos-1.example.com@EXAMPLE.COM
28 On a slave, the argument master specifies the hostname of the master
29 server from which to receive updates.
30 In contrast to hprop(8), which sends the whole database to the slaves
32 regularly, iprop normally sends only the changes as they happen on the
33 master. The master keeps track of all the changes by assigning a version
34 number to every transaction to the database. The slaves know which was
35 the latest version they saw, and in this way it can be determined if they
36 are in sync or not. A log of all the transactions is kept on the master.
37 When a slave is at an older version than the oldest one in the log, the
38 whole database has to be sent.
39 The log of transactions is also used to implement a two-phase commit
41 (with roll-forward for recovery) method of updating the HDB. Transac‐
42 tions are first recorded in the log, then in the HDB, then the log is
43 updated to mark the transaction as committed.
44 The changes are propagated over a secure channel (on port 2121 by
46 default). This should normally be defined as “iprop/tcp” in
47 /etc/services or another source of the services database. The master and
48 slaves must each have access to a keytab with keys for the iprop service
49 principal on the local host.
50 There is a keep-alive feature logged in the master's slave-stats file
52 (e.g. /var/heimdal/slave-stats).
53 Supported options for ipropd-master:
55 -c string, --config-file=string
57 -r string, --realm=string
59 -k kspec, --keytab=kspec
61 keytab to get authentication from
62 -d file, --database=file
64 Database (default per KDC)
65 --slave-stats-file=file
67 file for slave status information
68 --time-missing=time
70 time before slave is polled for presence (default 2 min)
71 --time-gone=time
73 time of inactivity after which a slave is considered gone
74 (default 5 min)
75 --detach
77 detach from console
78 --version
80 --help
82 Supported options for ipropd-slave:
84 -c string, --config-file=string
86 -r string, --realm=string
88 -k kspec, --keytab=kspec
90 keytab to get authentication from
91 --time-lost=time
93 time before server is considered lost (default 5 min)
94 --detach
96 detach from console
97 --version
99 --help
101 Time arguments for the relevant options above may be specified in forms
102 like 5 min, 300 s, or simply a number of seconds.
103
105 slaves, slave-stats in the database directory. ipropd-master.pid,
106 ipropd-slave.pid in the database directory, or in the directory named by
107 the HEIM_PIDFILE_DIR environment variable.
108
110 krb5.conf(5), hprop(8), hpropd(8), iprop-log(8), kdc(8).
111BSD May 24, 2005 BSD