[Solved] bind only using 1 CPU when chrooted (perfect server setup etch) I am running Debian Etch 64bit on an Athlon 64 x2. After installing bind, I get this in syslog: When bind runs chrooted (see http://www.howtoforge.com/perfect_setup_debian_etch_p4), it only detects 1 CPU. I think this user has the same problem: http://groups.google.com/group/comp.protocols.dns.bind/browse_thread/thread/4aab4b2a0ad4a3e0 The solution (see above link) was mounting /proc in chroot: But another user had some security concerns, so that they advise to mount read-only: Now, I have done the following: 1. mkdir /var/lib/named/proc 2. mount --bind /proc /var/lib/named/proc Syslog: Looks good, but is it really correct? And, how do I mount read-only? Thank you!