bind9/bin/tests/system/dupsigs/setup.sh

# 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.

SYSTEMTESTTOP=..
. $SYSTEMTESTTOP/conf.sh

$SHELL clean.sh

test -r $RANDFILE || $GENRANDOM 800 $RANDFILE

copy_setports ns1/named.conf.in ns1/named.conf

cp -f ns1/signing.test.db.in ns1/signing.test.db
(cd ns1; $SHELL ./reset_keys.sh)
add duplicate signature test 2018-05-03 02:50:32 -04:00			`# 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.`

			`SYSTEMTESTTOP=..`
			`. $SYSTEMTESTTOP/conf.sh`

Call clean.sh from all relevant setup.sh scripts For all system tests utilizing named instances, call clean.sh from each test's setup.sh script in a consistent way to make sure running the same system test multiple times using run.sh does not trigger false positives caused by stale files created by previous runs. Ideally we would just call clean.sh from run.sh, but that would break some quirky system tests like "rpz" or "rpzrecurse" and being consistent for the time being does not hurt. 2019-02-28 06:33:07 -05:00			`$SHELL clean.sh`
add duplicate signature test 2018-05-03 02:50:32 -04:00
			`test -r $RANDFILE \|\| $GENRANDOM 800 $RANDFILE`

			`copy_setports ns1/named.conf.in ns1/named.conf`

			`cp -f ns1/signing.test.db.in ns1/signing.test.db`
			`(cd ns1; $SHELL ./reset_keys.sh)`