Yes, so basically we have:
- dnsmasq.pid (create + read/write by dnsmasq)
- dnsmasq.raw (read by dnsmasq)
- dnsmasq.hosts (read by dnsmasq)
- dnsmasq.leases (create + read/write by dnsmasq)
I'd be tempted to just go with:
That should make things a bit more future proof should we add any more
dnsmasq related files in there.
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
In 16.10, LXD won't work with enforced dsnmasq profile
Status in AppArmor:
Status in apparmor package in Ubuntu:
After upgrading to 16.0, LXD networking stopped working due to
enforced dnsmasq profile.
audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED"
comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp