On Wed, Nov 23, 2005 at 11:51:21AM +0100, Stefan Schmidt wrote:
> Now that you mention it, i remember i have seen recent BIND9 implementations
> reporting they found only one cpu on a dual-processor machine. I think it was
> 9.3.2b1. Specifying the number of processors via cmdline option "-n 2" should
> temporarily solve this problem for you Rick, please report back if it does as
> i am running all of my high workload machines with --disable-threads making
> use of the ISC_INTERNAL_MALLOC routine Jinmei told me about on this list early
> this year.
> Sorry i didn't report this earlier, iirc i was in a hurry getting something
> fixed. I'll test the behaviour 9.3.2b2 on this right away.
                                      ^^s/b2/rc1/
Nov 23 11:58:48 cns1 named[18554]: starting BIND 9.3.2rc1 -t /var/named -u
bind
Nov 23 11:58:48 cns1 named[18554]: found 1 CPU, using 1 worker thread

compiled with:
./configure --prefix=/usr --sysconfdir=/etc/namedb --localstatedir=/var
--enable-threads --enable-libbind --enable-ipv6 --with-openssl=no
gcc version 4.0.2 (Debian 4.0.2-2)
Thread model: posix
# grep "^process" /proc/cpuinfo |wc -l
2
vendor_id       : GenuineIntel
cpu family      : 6
model           : 8
model name      : Pentium III (Coppermine)
stepping        : 3
cpu MHz         : 795.870
cache size      : 256 KB

	Stefan
-- 
A common mistake that people make when trying to design something completely
foolproof, is to underestimate the ingenuity of complete fools.
- Douglas Adams, "Mostly Harmless"