Report a bug: multi-threads of rndc-confgen can't work

Adam Tkac atkac at redhat.com
Tue Apr 15 08:44:38 UTC 2008


On Tue, Apr 15, 2008 at 04:23:13PM +0800, J. Peng wrote:
> I'm sorry that,  after I tested it again and again, "rndc-confgen"
> does can work, but it takes so looong time to get the results.
> You could see this:
> 
> # time ./rndc-confgen
> # Start of rndc.conf
> key "rndc-key" {
>         algorithm hmac-md5;
>         secret "CDSOyI64uu+0ZNN6i01hLg==";
> };
> 
> options {
>         default-key "rndc-key";
>         default-server 127.0.0.1;
>         default-port 953;
> };
> # End of rndc.conf
> 
> # Use with the following in named.conf, adjusting the allow list as needed:
> # key "rndc-key" {
> #       algorithm hmac-md5;
> #       secret "CDSOyI64uu+0ZNN6i01hLg==";
> # };
> #
> # controls {
> #       inet 127.0.0.1 port 953
> #               allow { 127.0.0.1; } keys { "rndc-key"; };
> # };
> # End of named.conf
> 
> real    2m26.489s
> user    0m0.000s
> sys     0m0.008s
> 
> 
> Need more than 2 minutes to get the output.
> Why this happen? Thanks.
> 
> (My OS is Suse Linux:
> # uname -a
> Linux bind2 2.6.16.21-0.8-TC #1 SMP Sat Jan 13 19:17:08 CST 2007 i686
> i686 i386 GNU/Linux )
> 
> On Tue, Apr 15, 2008 at 3:49 PM, J. Peng <peng.kyo at gmail.com> wrote:
> > I have tried to install and run bind-9.4.2 with multi-threads under
> >  Suse Linux, the kernel is 2.6.16.21.
> >  When I run "rndc-confgen" command for the first time, it can't work.
> >  Then I switched back to the mode without multi-threads, it works fine.
> >
> >  The "strace" results for that command are:
> 

I think your system doesn't have enough entropy. Did you try run
rndc-confgen tool with -r /dev/urandom?

Adam

---
Adam Tkac, Red Hat, Inc.


More information about the bind-users mailing list