(In reply to comment #28)
> This problem is still present with : 32:bind-9.8.2-0.10.rc1.el6_3.2.x86_64
> on CentOs 6.3, on two different servers
>
> I solved the problem by means of :
>
> chown -R named.named /var/named/chroot
>
> restorecon -R /var/named/chroot/
That helps for bind-9.9.1-5.P2.fc17.x86_64 in Fedora 17.
My custom named.conf was missing the:
managed-keys-directory "/var/named/dynamic";
mentioned in comment #29, but adding that and chown&restorecon makes CPU idle properly.
There is surely some sort of bug in bind. It needs access to something, but it cannot complain about the fact and starts chewing CPU. Please fix this.
(In reply to comment #28) 9.8.2-0. 10.rc1. el6_3.2. x86_64
> This problem is still present with : 32:bind-
> on CentOs 6.3, on two different servers
>
> I solved the problem by means of :
>
> chown -R named.named /var/named/chroot
>
> restorecon -R /var/named/chroot/
That helps for bind-9. 9.1-5.P2. fc17.x86_ 64 in Fedora 17.
My custom named.conf was missing the: keys-directory "/var/named/ dynamic" ;
managed-
mentioned in comment #29, but adding that and chown&restorecon makes CPU idle properly.
There is surely some sort of bug in bind. It needs access to something, but it cannot complain about the fact and starts chewing CPU. Please fix this.