From owner-freebsd-questions Wed Apr 17 05:54:55 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA05296 for questions-outgoing; Wed, 17 Apr 1996 05:54:55 -0700 (PDT) Received: from aries.ai.net ([205.252.67.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA05290 for ; Wed, 17 Apr 1996 05:54:52 -0700 (PDT) Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id IAA03200; Wed, 17 Apr 1996 08:53:43 -0400 Date: Wed, 17 Apr 1996 08:53:41 -0400 (EDT) From: Network Coordinator To: David Greenman cc: "Marc G. Fournier" , freebsd-questions@freebsd.org Subject: Re: Automatic Reboots and Locking up. In-Reply-To: <199604170250.TAA05027@Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > It's "no buffer space available". Do you use NFS heavily? If so, that could > be your problem. There are a variety of bugs in NFS that causes it to hang the > machine when used heavily. Casual use seems to be fine, it's only when > multiple processes start accessing files that it becomes a problem. > Well actually only one directory tree is mounted on that system, and (of course) its the tree that is used by the WWW server. It isn't used very often, but when it is, its hit pretty hard. I disabled it all (NFS that is) and the 12 hr reboots (because I was sick of cold-starting it) If mbufs clusters aren't a problem, and NFS isn't an issue, hopefully this thing will stay up and happy. (I even had the thing emailing me a copy of its netstat -m just before it rebooted and verified that wasn't a problem) Thanks for your time and insight, Paul