Ondřej Surý b29059b391 Test for the hard fetchlimit instead of soft fetchlimit ... Previously, the fetchlimit tested the recursive-clients soft limit that's defined as 90% of the hard limit (the actual configured value). This worked previously because the reaping of the oldest recursive client was put on the same event queue as the current TCP client, thus the cleaning has happened before the new TCP client established a new connection. With the change in BIND 9.14 that added a multiple event queues the cleaning of the oldests clients is no longer synchronous and could happen stochastically making the soft limit testing fail often. The situation became even worse with the new networking manager, thus we change the system test to fail only if the hard limit bound is not honored. Changing the accounting of the already reaped TCP clients so the soft limit testing is possible again is out of the scope for this change. (cherry picked from commit c35a4e05fa)		2020-01-09 14:08:05 +01:00
..
ans4	Update license headers to not include years in copyright in all applicable files	2018-02-23 10:12:02 +01:00
ns1	update system tests so validation won't fail when using IANA key	2018-05-31 18:22:33 +02:00
ns2	update system tests so validation won't fail when using IANA key	2018-05-31 18:22:33 +02:00
ns3	add properly-formatted -D options to named.args files	2019-01-28 19:58:24 -08:00
clean.sh	update system tests so validation won't fail when using IANA key	2018-05-31 18:22:33 +02:00
prereq.sh	Add a Net::DNS prereq for digdelv, fetchlimit, rpzrecurse, and zero	2018-04-04 22:23:14 +02:00
setup.sh	Automatically run clean.sh from run.sh	2019-12-06 14:47:08 +01:00
tests.sh	Test for the hard fetchlimit instead of soft fetchlimit	2020-01-09 14:08:05 +01:00