From owner-freebsd-current Mon Aug 24 09:07:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18114 for freebsd-current-outgoing; Mon, 24 Aug 1998 09:07:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18081 for ; Mon, 24 Aug 1998 09:07:10 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA28618; Mon, 24 Aug 1998 12:06:20 -0400 (EDT) (envelope-from wollman) Date: Mon, 24 Aug 1998 12:06:20 -0400 (EDT) From: Garrett Wollman Message-Id: <199808241606.MAA28618@khavrinen.lcs.mit.edu> To: "Michael Imamura" Cc: freebsd-current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? In-Reply-To: <19980824152046.24903.qmail@hotmail.com> References: <19980824152046.24903.qmail@hotmail.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Would this be related to my problem of cron all of a sudden dying off > repeatedly, sometimes every few minutes, after the system has been > compiling for a while? Yes. If cron gets into this state, then it will segfault every five minutes as it attempts to run atrun. [I wrote:] >> No, this is the ``daemons dying'' bug which nobody has fixed yet. >> When the system runs out of swap, some random selection of processes >> which are in swap get corrupted. Usually this results in a daemon >> which dies whenever it fork()s, but sometimes it is manifested as >> other sorts of corruption. The message you see from realloc is >> indicative of a corrupted pointer. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message