Ondřej Surý 20ac73eb22 Improve the logging on failed TCP accept ... Previously, when TCP accept failed, we have logged a message with ISC_LOG_ERROR level. One common case, how this could happen is that the client hits TCP client quota and is put on hold and when resumed, the client has already given up and closed the TCP connection. In such case, the named would log: TCP connection failed: socket is not connected This message was quite confusing because it actually doesn't say that it's related to the accepting the TCP connection and also it logs everything on the ISC_LOG_ERROR level. Change the log message to "Accepting TCP connection failed" and for specific error states lower the severity of the log message to ISC_LOG_INFO.		2021-12-02 13:50:00 +01:00
..
bind9	Add 'tls' validation for XoT enabled primaries	2021-12-01 12:00:29 +02:00
dns	On non-matching answer, check for missed timeout	2021-12-01 11:45:55 -08:00
irs	Check parsed resconf values	2021-08-12 09:52:52 -07:00
isc	Improve the logging on failed TCP accept	2021-12-02 13:50:00 +01:00
isccc	Use #pragma once as header guards	2021-10-13 00:49:15 -07:00
isccfg	Integrate extended ACLs syntax featuring 'port' and 'transport' opts	2021-11-30 12:20:22 +02:00
ns	Integrate extended ACLs syntax featuring 'port' and 'transport' opts	2021-11-30 12:20:22 +02:00
.gitignore	The isc/platform.h header has been completely removed	2021-07-06 05:33:48 +00:00
Makefile.am	move samples/resolve.c to bin/tests/system	2021-04-16 14:29:43 +02:00
unit-test-driver.sh.in	Enforce a run time limit on unit test binaries	2021-04-07 11:41:45 +02:00