Michał Kępień 5cc841fa53 Reset dig exit code after a TCP connection is established ... The "exitcode" variable is set to 9 if a TCP connection fails, but is not reset to 0 if a subsequent TCP connection succeeds. This causes dig to return a non-zero exit code if it succeeds in getting a TCP response after a retry. Fix by resetting "exitcode" to 0 if connect_done() receives an event with the "result" field set to ISC_R_SUCCESS. (cherry picked from commit deb3b85cb2)		2018-08-27 14:30:06 +10:00
..
check	Replace custom isc_boolean_t with C standard bool type	2018-08-10 11:17:51 +02:00
confgen	Replace custom isc_boolean_t with C standard bool type	2018-08-10 11:17:51 +02:00
delv	Replace custom isc_boolean_t with C standard bool type	2018-08-10 11:17:51 +02:00
dig	Reset dig exit code after a TCP connection is established	2018-08-27 14:30:06 +10:00
dnssec	Replace custom isc_boolean_t with C standard bool type	2018-08-10 11:17:51 +02:00
named	Log a message when "ixfr-from-differences" is set for an inline-signed zone	2018-08-24 10:21:27 +02:00
nsupdate	Replace custom isc_boolean_t with C standard bool type	2018-08-10 11:17:51 +02:00
pkcs11	Replace custom isc_boolean_t with C standard bool type	2018-08-10 11:17:51 +02:00
python	Revert "Use make automatic variables to install updated manuals"	2018-08-06 12:51:07 +02:00
rndc	Replace custom isc_boolean_t with C standard bool type	2018-08-10 11:17:51 +02:00
tests	Do not call bin/tools/genrandom unconditionally in system tests	2018-08-24 09:57:15 +02:00
tools	Whitespace fixes	2018-08-24 08:34:44 -04:00
win32/BINDInstall	Remove $Id markers, Principal Author and Reviewed tags from the full source tree	2018-05-11 14:19:35 +02:00
Makefile.in	reduce race risk in parallel builds	2018-03-09 14:40:10 -08:00