summaryrefslogtreecommitdiffstats
path: root/src/include/kdb_log.h
diff options
context:
space:
mode:
authorNicolas Williams <nico@cryptonector.com>2012-09-20 15:37:45 -0400
committerGreg Hudson <ghudson@mit.edu>2012-10-05 15:20:46 -0400
commit969331732b62e73d1e073ff3ad87bf1774ee9fd1 (patch)
treeb983135735d12c96203c9a350a241a9de2a66756 /src/include/kdb_log.h
parent1d7c107c9e9239674b5c7aed32931ab47c50f239 (diff)
downloadkrb5-969331732b62e73d1e073ff3ad87bf1774ee9fd1.tar.gz
krb5-969331732b62e73d1e073ff3ad87bf1774ee9fd1.tar.xz
krb5-969331732b62e73d1e073ff3ad87bf1774ee9fd1.zip
Make kadmind iprop never return UPDATE_BUSY
Currently kadmind allows slaves to poll for updates as often as they like, but not within 10s of the last update. This means that iprop will appear to fail to synchronize the KDC at any site whose master KDC processes at least one write transaction every 10 seconds consistently. The original intention must have been to throttle iprop clients (slave KDCs) that poll too often. But UPDATE_BUSY as implemented is not that, and implementing a throttle would be difficult (requires keeping state in a table) and mostly useless (admins can manage their poll timers just fine without a throttle in kadmind). ticket: 7369
Diffstat (limited to 'src/include/kdb_log.h')
0 files changed, 0 insertions, 0 deletions