Is this something required for later versions of BIND?

I have BIND 9.2.x on Linux systems in chroot environments but never had
to mount /proc there. Since /proc isn't a "real" filesystem I was
under the impression the kernel handled most of what needs to go there.
Exceptions would be the things one does to force updates in the rare
areas (e.g. SCSI changes) /proc allows that. What would BIND be doing
that requires it to directly access /proc?

-----Original Message-----
From: [] On
Behalf Of Adam Tkac
Sent: Tuesday, April 01, 2008 8:23 AM
To: greg kuechle
Subject: Re: Number of CPUs detected by Bind 9.4.2 on 4 CPU system
runningRedHat es 4.

On Mon, Mar 31, 2008 at 11:59:10AM -0600, greg kuechle wrote:
> Hello,
> I have install bind 9.4.2 on a system with 4 CPUs running RedHat es4.

> compiled named with the --enable-threads and used the -n 4 flag when

> start named.
> Mar 31 10:12:24 ******** named[4897]: starting BIND 9.4.2 -t

> -u named -n 4 -c /etc/named.conf
> Mar 31 16:12:24 ******** named[4897]: found 1 CPU, using 4 worker

> Before I upgraded the system it was running an older version of named

> comes packaged with the OS.
> Here is the output from the logfile.
> Mar 24 11:34:13 ******** named[5877]: starting BIND 9.2.4
> Mar 24 11:34:13 ******** named[5877]: using 4 CPUs
> Did I compile named wrong?
> Will BIND 9.4.2 use all of the CPUs if I use the -n 4 option at

> It looks like named is only running on one CPU. Will named start using

> other CPUs once one CPU is up to 100% ?
> Thank you for any help.

I think you forgot mount /proc filesystem into chroot. You can try it
with /proc mounted in chroot (for example $mount --bind /proc


Adam Tkac, Red Hat, Inc.
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.