From owner-freebsd-current Sun Dec 6 22:03:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21057 for freebsd-current-outgoing; Sun, 6 Dec 1998 22:03:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phantasm.thekeep.org (PHANTASM.CC.CMU.EDU [128.2.35.108]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA21051 for ; Sun, 6 Dec 1998 22:03:29 -0800 (PST) (envelope-from dar@thekeep.org) Received: (qmail 77885 invoked by uid 100); 7 Dec 1998 06:03:26 -0000 Message-ID: <19981207010325.A39345@thekeep.org> Date: Mon, 7 Dec 1998 01:03:25 -0500 From: Dan Root To: current@FreeBSD.ORG Subject: status of dying daemons bug? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been watching the mailing list fairly closely for the past month or so, but don't remember seeing a definitive solution to the dying daemon problem. I'm still having the problem here, with -current sources built yesterday. I'm not quite sure why I'm ever hitting swap, given the machine's load (almost never more than 80 or 100 megs of active memory on a P6-SMP machine with 256), but the instant I do, I begin seeing the problem. It's nearly 100% reliable, even if only a few hundred kilobytes are swapped out. Right now I'm doing 'sysctl -w vm.disable_swapspace_pageouts=1' just to keep the machine up and running, but this is hardly a good long term solution. Unfortunately I lack the familiarity with the VM internals to go hunting after this myself. However, I would be more than willing to assist someone in finding the problem, including giving people access to my machine so they can poke around. I'd also be happy to post kernel config files, output from vmstat and friends, or anything else that might help. -DaR -- Dan Root - dar@thekeep.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message