@Christian Adding the rc.conf file should be enough but unless you add
/run/systemd/notify w, unbound won't get far enough to trigger the chown issue. ---- For the second issue, change the 'deny capability chown,' to 'capability chown,' in the unbound apparmor profile, restart apparmor and restart unbound. It should log the fowner error. Unfortunately, I'm not sure what side effect changing that line will have. Simon can probably tell us more as he is the one who adds it in the first place: https://bazaar.launchpad.net/~sdeziel/apparmor-profiles/unbound- chown/revision/169 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749931 Title: unbound-control local socket broken by apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1749931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
