From owner-freebsd-stable Mon Dec 27 20:32:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 0188C14D09; Mon, 27 Dec 1999 20:32:11 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id XAA22968; Mon, 27 Dec 1999 23:32:18 -0500 (EST) Date: Mon, 27 Dec 1999 23:32:18 -0500 (EST) From: "Mr. K." To: Mike Smith Cc: stable@freebsd.org Subject: Re: panic In-Reply-To: <199912280428.UAA00870@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have > > to tweak anything to make the kernel not panic, though... Not > > complaining, just pre-empting possible flames. > > That's completely incorrect. > > > Is this a known problem? Yes, I should enable crash dumps, I'm going to > > go look for documentation on that now... > > You might just try watching the console when the system goes over. > GENERIC is tuned to work well on a wide range of configurations, not to > be pounded to death. Try setting NMBCLUSTERS to something around 10000. > Ran to the machine as soon as I realized what happened, but unfortunately, too late. I was not root when this happened, so, basically, you're saying that freebsd is not meant for a production environment where untrusted users have telnet access? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message