From owner-freebsd-hackers  Sat Jan 14 09:46:09 1995
Return-Path: hackers-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA00983 for hackers-outgoing; Sat, 14 Jan 1995 09:46:09 -0800
Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA00977 for <FreeBSD-hackers@freefall.cdrom.com>; Sat, 14 Jan 1995 09:46:06 -0800
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id JAA05859; Sat, 14 Jan 1995 09:46:02 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id JAA02308; Sat, 14 Jan 1995 09:46:02 -0800
Message-Id: <199501141746.JAA02308@corbin.Root.COM>
X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol
To: guido@gvr.win.tue.nl (Guido van Rooij)
cc: FreeBSD-hackers@freefall.cdrom.com (FreeBSD-hackers)
Subject: Re: these damn signals 10 and 11 
In-reply-to: Your message of "Sat, 14 Jan 95 16:31:19 +0100."
             <199501141531.QAA29161@gvr.win.tue.nl> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sat, 14 Jan 1995 09:46:01 -0800
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>What does it mean when the kernel starts killing proceses 
>with signals 10 and 11? The system is not out of memory or swapsapce.
>The system is a 486 66MHz that is runnng 2.0R. Any known problems in
>the vm area?

   Probably. We've fixed problems that could cause this. 2.0 was definately a
bit rough around the edges...which is why we've recommended to people that
really need stability to stick with 1.1.5+patches. The promise of 2.1 is
stability and better performance. The *next* 2.1 snapshot should be fairly
stable - we're working on this, anyway.

-DG