From owner-freebsd-security Thu Oct 7 13:53:39 1999 Delivered-To: freebsd-security@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 4D9661525E for ; Thu, 7 Oct 1999 13:53:29 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id WAA16006; Thu, 7 Oct 1999 22:51:01 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id WAA34502; Thu, 7 Oct 1999 22:51:00 +0200 (MET DST) Date: Thu, 7 Oct 1999 22:50:59 +0200 From: Eivind Eklund To: Brett Glass Cc: Adam , security@FreeBSD.ORG Subject: Re: Random malfunction or hack? Message-ID: <19991007225059.P71340@bitbox.follo.net> References: <4.2.0.58.19991007104520.043fbbb0@localhost> <4.2.0.58.19991007120245.041a87d0@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <4.2.0.58.19991007120245.041a87d0@localhost> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Oct 07, 1999 at 12:13:47PM -0600, Brett Glass wrote: > At 02:00 PM 10/7/99 -0400, Adam wrote: > > >What version of FreeBSD? > > 2.2.8-RELEASE, with added patches to fix a known bug or three. Sound very much like a (now fixed) VM bug which triggers very seldom, which leads to page table corruption (IIRC) which trigger on fork(). If this was the case, killing and restarting cron would have fixed it. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message