From: Evan Hunt Date: Mon, 20 Jul 2015 22:25:28 +0000 (-0700) Subject: [master] remove accidentally duplicated section on clients-per-query X-Git-Tag: v9.11.0a1~645 X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=8a205b45347e1609cdcb853aecc926b8b7f2c1b8;p=thirdparty%2Fbind9.git [master] remove accidentally duplicated section on clients-per-query --- diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index b99797d7070..770dbc88d3c 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -4982,8 +4982,6 @@ badresp:1,adberr:0,findfail:0,valfail:0] acache-enable yes_or_no ; acache-cleaning-interval number; max-acache-size size_spec ; - clients-per-query number ; - max-clients-per-query number ; max-recursion-depth number ; max-recursion-queries number ; masterfile-format @@ -9375,42 +9373,6 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; - - clients-per-query - max-clients-per-query - - These set the - initial value (minimum) and maximum number of recursive - simultaneous clients for any given query - (<qname,qtype,qclass>) that the server will accept - before dropping additional clients. - named will attempt to - self tune this value and changes will be logged. The - default values are 10 and 100. - - - This value should reflect how many queries come in for - a given name in the time it takes to resolve that name. - If the number of queries exceed this value, named will - assume that it is dealing with a non-responsive zone - and will drop additional queries. If it gets a response - after dropping queries, it will raise the estimate. The - estimate will then be lowered in 20 minutes if it has - remained unchanged. - - - If clients-per-query is set to zero, - then there is no limit on the number of clients per query - and no queries will be dropped. - - - If max-clients-per-query is set to zero, - then there is no upper bound other than imposed by - recursive-clients. - - - - max-recursion-depth