Date: Sat, 21 Nov 1998 10:40:48 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Eivind Eklund <eivind@yes.no> Cc: Barrett Richardson <terbart@aye.net>, garman@earthling.net, current@FreeBSD.ORG Subject: Re: more dying daemons Message-ID: <199811211840.KAA24741@apollo.backplane.com> References: <199811210418.UAA06160@hub.freebsd.org> <Pine.BSF.3.96.981121025345.26942A-100000@phoenix.aye.net> <19981121164344.E17306@follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
: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.
<dillon@backplane.com> (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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811211840.KAA24741>