004849fd36
This test ensures that named will correctly shutdown
when receiving multiple control connections after processing
of either "rncd stop" or "kill -SIGTERM" commands.
Before the fix, named was crashing due to a race condition happening
between two threads, one running shutdown logic in named/server.c
and other handling control logic in controlconf.c.
This test tries to reproduce the above scenario by issuing multiple
queries to a target named instance, issuing either rndc stop or kill
-SIGTERM command to the same named instance, then starting multiple rndc
status connections to ensure it is not crashing anymore.
(cherry picked from commit 042e509753)
19 lines
556 B
Bash
19 lines
556 B
Bash
# Copyright (C) Internet Systems Consortium, Inc. ("ISC")
|
|
#
|
|
# This Source Code Form is subject to the terms of the Mozilla Public
|
|
# License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
|
|
#
|
|
# See the COPYRIGHT file distributed with this work for additional
|
|
# information regarding copyright ownership.
|
|
|
|
rm -f ns*/*.jnl
|
|
rm -f ns*/named.conf
|
|
rm -f ns*/named.lock
|
|
rm -f ns*/named.memstats
|
|
rm -f ns*/named.run
|
|
rm -f ns*/rpz*.txt
|
|
rm -f resolver/named.conf
|
|
rm -rf __pycache__
|
|
rm -f *.status
|