Matthijs Mekking b9ebde705b Add system test lingering CLOSE_WAIT TCP sockets ... Add a test case to check for lingering TCP sockets stuck in the CLOSE_WAIT state. This can happen if a client sends some garbage after its first query. The system test runs the reproducer script and then sends another TCP query to the resolver. The resolver is configured to allow one TCP client only. If BIND has its TCP socket stuck in CLOSE_WAIT, it does not have the resources available to answer the second query. Note: A better test would be to check if the named daemon does not have a TCP socket stuck in CLOSE_WAIT for example with netstat. When running this test locally you can examine named with netstat manually. But since netstat is platform specific it is not a good candidate to do this as a system test. If you, if you could return, don't let it burn. Do you have to let it linger? - Cranberries		2022-04-07 17:02:48 +02:00
..
check	Set hard thread affinity for each zone	2022-04-01 23:50:34 +02:00
confgen	Replace ISC_NORETURN with C11's noreturn	2022-03-25 08:33:43 +01:00
delv	Remove isc_appctx_t use in dns_client	2022-03-29 14:14:49 -07:00
dig	Fix using unset pointer when printing a debug message in dighost.c	2022-04-05 11:20:42 +00:00
dnssec	Teach dnssec-settime to read times that it writes	2022-03-25 16:05:43 +01:00
named	Rename the configuration option to load balance sockets to reuseport	2022-04-06 17:03:57 +02:00
nsupdate	Remove use of the inline keyword used as suggestion to compiler	2022-03-25 08:33:43 +01:00
plugins	Make isc_ht optionally case insensitive	2022-03-28 15:02:18 -07:00
rndc	Remove extrahandle size from netmgr	2022-03-25 10:38:35 +01:00
tests	Add system test lingering CLOSE_WAIT TCP sockets	2022-04-07 17:02:48 +02:00
tools	Ensure that dns_request_createvia() has a retry limit	2022-04-06 17:12:48 +01:00
Makefile.am	Remove native PKCS#11 support	2021-09-09 15:35:39 +02:00