add some text about automating propagation
git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@8732 ec53bebd-3082-4978-b11e-865c3cabbd6b
This commit is contained in:
@@ -274,7 +274,7 @@ Every slave needs a keytab with a principal,
|
|||||||
@code{propd}, as follows:
|
@code{propd}, as follows:
|
||||||
|
|
||||||
@example
|
@example
|
||||||
slave# ktutil get -p foo/admin host/slave
|
slave# ktutil get -p foo/admin host/`hostname`
|
||||||
slave# hpropd
|
slave# hpropd
|
||||||
@end example
|
@end example
|
||||||
|
|
||||||
@@ -290,3 +290,13 @@ Then run
|
|||||||
@example
|
@example
|
||||||
master# hprop slave
|
master# hprop slave
|
||||||
@end example
|
@end example
|
||||||
|
|
||||||
|
This was just an on-hands example to make sure that everything was
|
||||||
|
working properly. Doing it manually is of course the wrong way and to
|
||||||
|
automate this you will want to start
|
||||||
|
@pindex hpropd
|
||||||
|
@code{hpropd} from @code{inetd} on the slave(s) and regularly run
|
||||||
|
@pindex hprop
|
||||||
|
@code{hprop} on the master to regularly propagate the database.
|
||||||
|
Starting the propagation once an hour from @code{cron} is probably a
|
||||||
|
good idea.
|
||||||
|
Reference in New Issue
Block a user