summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDave Page2012-01-06 09:33:37 +0000
committerDave Page2012-01-06 09:33:37 +0000
commit8cf89e5e5d2c455b78076306386263c3ef97b4a9 (patch)
treefff8e216c9284aa2f0b084c0cb9196ee870e11db
parent544f35c900324165cd82c1a2337660de2f5cb870 (diff)
Fix documentation regarding reenabling of flapping servers.HEADmaster
-rw-r--r--README3
1 files changed, 1 insertions, 2 deletions
diff --git a/README b/README
index ce35fec..3832601 100644
--- a/README
+++ b/README
@@ -35,8 +35,7 @@ The automatic mirror systems works like this, in a few short points:
* A very simple flap detection algorithm is run after all servers have been
scanned. If a server has changed state too many times in a specified interval,
the server is listed as flapping. In this case, it will not be included in the
- zone and it will *NOT* be automatically re-enabled. Flapping servers have to
- be manually enabled.
+ zone and it will be automatically re-enabled aafter 24 hours.
* If any data has changed due to this, the zone is reloaded in the nameserver,
and propagates to all the clients based on DNS NOTIFY messages.