Tom Haapanen writes:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Our web server (164SX/533, 256 MB, NetBSD 1.4.1) got these early this
> morning and promptly fell off the network:
> 
> Mar  9 01:57:37 stratos /netbsd: WARNING: mclpool limit reached; increase
> NMBCLUSTERS 
> Mar  9 01:59:10 stratos /netbsd: WARNING: mclpool limit reached; increase
> NMBCLUSTERS
> 
> How do I determine what my current NMBCLUSTERS is actually set to?  How high
> should I set it to be safe?

On an i386 box (P133, 100 Mbps 'de') that was getting hammered with DNS,
I upped it to 16384 and it works fine now.

This makes a good "denial of service" attack IMHO.  Your server happily
runs along with 'NMBCLUSTERS=1024' for months, and suddenly you lose access
to it, have have to rebuild a kernel with 2048.  Oops, that isn't enough,
lost access again, try 4096, oops, 8192, oops, 16384.  Whew!  Damn thing
is "stable" again.

-Andrew
-- 
-----------------------------------------------------------------
Andrew Gillham                            | This space left blank
gillham@whirlpool.com                     | inadvertently.
I speak for myself, not for my employer.  | Contact the publisher.