From owner-freebsd-current  Sat Jul 11 04:10:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA25508
          for freebsd-current-outgoing; Sat, 11 Jul 1998 04:10:22 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25502
          for <current@FreeBSD.ORG>; Sat, 11 Jul 1998 04:10:20 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA15688;
	Sat, 11 Jul 1998 04:10:56 -0700 (PDT)
Message-Id: <199807111110.EAA15688@implode.root.com>
To: Terry Lambert <tlambert@primenet.com>
cc: current@FreeBSD.ORG
Subject: Re: Arrgh ! resubscribing again again again.... 
In-reply-to: Your message of "Sat, 11 Jul 1998 09:25:11 -0000."
             <199807110925.CAA16987@usr08.primenet.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sat, 11 Jul 1998 04:10:56 -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>When no backing pages exist (becaues you've used them all up and are
>out of swap space), the process requesting the page as a result of
>the copy on write fault can not have its request satisfied.
>
>The result of an unsatified fault request is a SIGSEGV, or signal 11;

   Wrong. The result of running out of swap space is a SIGKILL, or signal 9.
The bug that people are refering to seems to have been introduced around the
time that John was messing with the VM map code, but might predate that to
when he was messing with some of the swap pager algorithms.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message