From c17be6c62f66e7449f25d1f4c35f0f8a8b72c9ba Mon Sep 17 00:00:00 2001 From: Assar Westerlund Date: Fri, 21 Jul 2000 04:06:26 +0000 Subject: [PATCH] add some text about automating propagation git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@8732 ec53bebd-3082-4978-b11e-865c3cabbd6b --- doc/setup.texi | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/doc/setup.texi b/doc/setup.texi index 12fe101ec..1222eccbe 100644 --- a/doc/setup.texi +++ b/doc/setup.texi @@ -274,7 +274,7 @@ Every slave needs a keytab with a principal, @code{propd}, as follows: @example -slave# ktutil get -p foo/admin host/slave +slave# ktutil get -p foo/admin host/`hostname` slave# hpropd @end example @@ -290,3 +290,13 @@ Then run @example master# hprop slave @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.