Bug#947771: unbound: cannot restart daemon under sysvinit-core when apparmor is enforced

2021-10-26 Thread Simon Deziel
I took the patch from Gedalya and proposed it: https://salsa.debian.org/dns-team/unbound/-/merge_requests/17

Bug#947771: unbound: cannot restart daemon under sysvinit-core when apparmor is enforced

2021-10-25 Thread Dominik
Followup-For: Bug #947771 Package: unbound Version: 1.13.1-1 On Thu, 28 Jan 2021 02:19:05 +0800 Gedalya wrote: --- unbound.init    2020-12-24 00:34:24.0 + +++ /etc/init.d/unbound    2021-01-27 18:15:25.663526469 + @@ -42,7 +42,7 @@ stop) log_daemon_msg

Bug#947771: unbound: cannot restart daemon under sysvinit-core when apparmor is enforced

2021-09-26 Thread Roger Lynn
Followup-For: Bug #947771 Package: unbound Version: 1.13.1-1 On Fri, 03 Jul 2020 19:27:17 +0900 Stephane Lapie wrote: I worked around this issue by adding --remove-pidfile to the "start-stop-daemon --stop" commands. On Thu, 28 Jan 2021 02:19:05 +0800 Gedalya wrote: -    if

Bug#947771: unbound: cannot restart daemon under sysvinit-core when apparmor is enforced

2021-01-27 Thread Gedalya
Hello, I find the following is enough: --- unbound.init    2020-12-24 00:34:24.0 + +++ /etc/init.d/unbound    2021-01-27 18:15:25.663526469 + @@ -42,7 +42,7 @@   stop) log_daemon_msg "Stopping $DESC" "$NAME" -    if start-stop-daemon --stop --quiet --oknodo

Bug#947771: unbound: cannot restart daemon under sysvinit-core when apparmor is enforced

2019-12-30 Thread g1
Package: unbound Version: 1.9.0-2+deb10u1 Severity: normal Tags: patch At startup the daemon creates its pidfile (/run/unbound.pid) while running as root, chown()s it to unbound:unbound, then drops privileges and runs as user unbound. At shutdown, the pidfile is successfully truncated, but the