From dd193d1279084e40ef902267a1cea0b6cc7f18fb Mon Sep 17 00:00:00 2001 From: Michael Lucas Date: Thu, 12 May 2005 20:55:55 +0000 Subject: [PATCH] We discuss increasing NMBCLUSTERS in the Handbook. Don't have separate, old instructions in the FAQ, point to the authoritative Handbook instead. --- en_US.ISO8859-1/books/faq/book.sgml | 16 +++------------- 1 file changed, 3 insertions(+), 13 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 9bca881f36..04976c4cda 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -3284,19 +3284,9 @@ quit The panic indicates that the system ran out of virtual memory for network buffers (specifically, mbuf clusters). You can increase the amount of VM available for mbuf clusters by - adding: - - options NMBCLUSTERS=n - - to your kernel config file, where - n is a number in the range - 512-4096, depending on the number of concurrent TCP - connections you need to support. We recommend trying - 2048 - this should get rid of the panic completely. You - can monitor the number of mbuf clusters allocated/in use - on the system with netstat -m (see - &man.netstat.1;). The default value for NMBCLUSTERS is - 1024 + MAXUSERS * 64. + following the instructions in the Network + Limits section of the Handbook.