switching from syslog to logfile changes what gets logged?

Unbound
1

Hi,

I intended to switch from syslog to a dedicated
logfile, without expecting any change on _what_ gets logged,
but noticed that when switching to the logfile
without increasing / changing verbosity the type of information
that is written to the logfile increased.

Is this a bug?
(verbosity was 2)

even in verbosity level 1 it generates strange multi-line log entries in dig-output format:

<timestamp> info: validator: error. failed to classify response message: ;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
[...]

unbound version: 1.9.1

kind regards,
nusenu

2

it looks like it is impossible to tell unbound that it
should under no circumstances log QNAMEs to the logfile
since it even happens with "verbosity 0"

I filed the following bugzilla entry:
https://nlnetlabs.nl/bugs-script/show_bug.cgi?id=4241