Open MMarco94 opened 2 years ago
I realize it's documented that unbound-control set_option
shouldn't work.
However, the same behavior happens when going from logfile
and use-syslog
(and viceversa) by editing the config and then calling unbound-control reload
: nothing happens until unbound-control log_reopen
is called
unbound-control reload will reopen logfile when use-syslog set to 0. However, I encountered a problem. The logfile failed to be opened, and errno was 13 (Permission denied). Even though I changed the owner group of the logfile to unbound.
Do not add the -d when execute unbound. The above error will be not reported.
为什么termux中启动一直报错
在termux中安装了unbound,pkg install unbound 并且正确配置了unbound.conf文件但是无法启动如上个评论所示 同时也获取了root权限
Describe the bug Changing
logfile
oruse-syslog
on unbound's config, and then callingunbound-control reload
doesn't work; the new setting gets applied only after either a restart or a call tounbound-control log_reopen
.The same also happens if those setting gets changed via
unbound-control set_option
.To reproduce Steps to reproduce the behavior:
Expected behavior Logs get written to
/tmp/unbound_log_test
. Actual behavior: log location doesn't change.Workaround Calling
unbound-control log_reopen
or restarting unbound.System:
unbound -V
output:Additional information N/A