Note that upgrades from Lucid to Precise can trigger this bug as the
directory permissions may preclude writing to /var/cache/bind - see bug
1086775
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Changed in: bind9 (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1038199
Title:
Bind9 9.8.1 high CPU utilization when managed-keys-directory
** Bug watch added: Debian Bug tracker #695264
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695264
** Also affects: bind9 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695264
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Looks to be well known though unaddressed upstream yet. Since it has a
reasonably simple workaround (use the managed-keys-directory option)
I've marked it as Medium.
** Summary changed:
- Bind9 9.8.1 high CPU utilization
+ Bind9 9.8.1 high CPU utilization when managed-keys-directory option is
I discovered this bug the hard way when I transferred over my named.conf
from a Ubuntu 10.04 LTS system to 12.04. The managed-keys-directory
option was not valid in 10.04 (Bind 9.7.0).
** Bug watch added: Red Hat Bugzilla #709205
https://bugzilla.redhat.com/show_bug.cgi?id=709205
** Also
