mirror of
https://github.com/isc-projects/bind9.git
synced 2026-02-26 11:32:01 -05:00
d934513c42
This commit ensures that dnstap output files captured by fstrm_capture are properly flushed before any attempt on reading them with dnstap-read is done. By reading fstrm-capture source code it was noticed that signal SIGHUP is used to flush the capture file. |
||
|---|---|---|
| .. | ||
| ns1 | ||
| ns2 | ||
| ns3 | ||
| ns4 | ||
| bad-fstrm-reopen-interval.conf | ||
| bad-fstrm-set-buffer-hint-max.conf | ||
| bad-fstrm-set-buffer-hint-min.conf | ||
| bad-fstrm-set-flush-timeout-max.conf | ||
| bad-fstrm-set-flush-timeout-min.conf | ||
| bad-fstrm-set-input-queue-size-max.conf | ||
| bad-fstrm-set-input-queue-size-min.conf | ||
| bad-fstrm-set-input-queue-size-po2.conf | ||
| bad-fstrm-set-output-notify-threshold.conf | ||
| bad-fstrm-set-output-queue-size-max.conf | ||
| bad-fstrm-set-output-queue-size-min.conf | ||
| bad-fstrm-set-reopen-interval-max.conf | ||
| bad-fstrm-set-reopen-interval-min.conf | ||
| bad-missing-dnstap-output-view.conf | ||
| bad-missing-dnstap-output.conf | ||
| bad-size-version.conf | ||
| clean.sh | ||
| good-dnstap-in-options.conf | ||
| good-dnstap-in-view.conf | ||
| good-fstrm-reopen-interval.conf | ||
| good-fstrm-set-buffer-hint.conf | ||
| good-fstrm-set-flush-timeout.conf | ||
| good-fstrm-set-input-queue-size.conf | ||
| good-fstrm-set-output-notify-threshold.conf | ||
| good-fstrm-set-output-queue-model-mpsc.conf | ||
| good-fstrm-set-output-queue-model-spsc.conf | ||
| good-fstrm-set-output-queue-size.conf | ||
| good-fstrm-set-reopen-interval.conf | ||
| good-size-unlimited.conf | ||
| good-size-version.conf | ||
| large-answer.fstrm | ||
| README | ||
| setup.sh | ||
| tests.sh | ||
| ydump.py | ||
Copyright (C) Internet Systems Consortium, Inc. ("ISC")
See COPYRIGHT in the source root or https://isc.org/copyright.html for terms.
The "large-answer.fstrm" file was generated by configuring a named instance
compiled with --enable-dnstap and --enable-fixed-rrset with the following
directives:
minimal-responses yes;
rrset-order { order fixed; };
dnstap { auth response; };
dnstap-identity none;
dnstap-output file "large-answer.fstrm";
The captured RRset from the "example." zone was created using:
$GENERATE 1-48 @ IN A 127.0.0.$
A server instance set up this way was then queried non-recursively (RD=0) for
"example/A".