aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKen Raeburn <raeburn@mit.edu>2008-06-23 20:05:45 +0000
committerKen Raeburn <raeburn@mit.edu>2008-06-23 20:05:45 +0000
commit417c99ad944f0cff2bbb527e7d79b010ebc41343 (patch)
tree67cc22e7cdb54f14de581df0a019d62fd3b02457
parentffde8c1e6f1500d42b6f8f9db8ff8dd3a4b68871 (diff)
downloadkrb5-417c99ad944f0cff2bbb527e7d79b010ebc41343.zip
krb5-417c99ad944f0cff2bbb527e7d79b010ebc41343.tar.gz
krb5-417c99ad944f0cff2bbb527e7d79b010ebc41343.tar.bz2
note current threshold for 'busy' database
git-svn-id: svn://anonsvn.mit.edu/krb5/branches/sun-iprop@20455 dc483132-0cff-0310-8789-dd5450dbe970
-rw-r--r--doc/install.texinfo11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/install.texinfo b/doc/install.texinfo
index 7413ad4..54f183d 100644
--- a/doc/install.texinfo
+++ b/doc/install.texinfo
@@ -1017,11 +1017,12 @@ size. A process on each slave KDC connects to a service on the master
KDC (currently implmented in the @code{kadmind} server) and
periodically requests the changes that have been made since the last
check. By default, this check is done every two minutes. If the
-database has just been modified in the previous several seconds, the
-slave will not retrieve updates, but instead will pause and try again
-soon after. This reduces the likelihood that incremental update
-queries will cause delays for an administrator trying to make a bunch
-of changes to the database at the same time.
+database has just been modified in the previous several seconds
+(currently the threshold is hard-coded at 10 seconds), the slave will
+not retrieve updates, but instead will pause and try again soon after.
+This reduces the likelihood that incremental update queries will cause
+delays for an administrator trying to make a bunch of changes to the
+database at the same time.
Incremental propagation uses the following entries in the per-realm
data in the KDC config file: