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
..
startperf	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
system	Add system test lingering CLOSE_WAIT TCP sockets	2022-04-07 17:02:48 +02:00
testdata/wire	move all optional tests from bin/tests to bin/tests/optional	2018-03-09 14:12:47 -08:00
.gitignore	Refactor TLSDNS module to work with libuv/ssl directly	2021-01-25 09:19:22 +01:00
convert-trs-to-junit.py	Generate JUnit reports for unit & system tests	2022-04-06 21:14:38 +02:00
Makefile.am	Avoid using C99 variable length arrays	2022-03-18 15:11:48 +00:00
test_client.c	Consistenly use UNREACHABLE() instead of ISC_UNREACHABLE()	2022-03-28 23:26:08 +02:00
test_server.c	Consistenly use UNREACHABLE() instead of ISC_UNREACHABLE()	2022-03-28 23:26:08 +02:00
wire_test.c	Remove UNREACHABLE() statements after exit()	2022-03-25 09:25:11 +01:00