From owner-freebsd-current Sat Nov 21 10:41:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07946 for freebsd-current-outgoing; Sat, 21 Nov 1998 10:41:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07939 for ; Sat, 21 Nov 1998 10:41:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id KAA24741; Sat, 21 Nov 1998 10:40:48 -0800 (PST) (envelope-from dillon) Date: Sat, 21 Nov 1998 10:40:48 -0800 (PST) From: Matthew Dillon Message-Id: <199811211840.KAA24741@apollo.backplane.com> To: Eivind Eklund Cc: Barrett Richardson , garman@earthling.net, current@FreeBSD.ORG Subject: Re: more dying daemons References: <199811210418.UAA06160@hub.freebsd.org> <19981121164344.E17306@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The bug in question is "new" (23rd february, most likely), and is not :visible in -stable. It is a serious bug. Saying that his swap usage :is 'too high' is not going to help us solve it; the system is supposed :to be stable no matter what. We can't take 3.0 to be -STABLE until :this bug and the clock bug is solved. : :Eivind. : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message We need to find a way to reproduce the problem. I'm running serveral -current systems, one very heavily (nntp1.ba.best.com), and swap utilization is normal. Is the original person who reported the problem using MFS mounts by any chance? -- I'm happy the clock cpu-resource problem has been fixed, that was starting to get annoying. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message