From owner-freebsd-current Tue Oct 13 03:54:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07780 for freebsd-current-outgoing; Tue, 13 Oct 1998 03:54:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA07770 for ; Tue, 13 Oct 1998 03:54:49 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id DAA12263; Tue, 13 Oct 1998 03:52:55 -0700 (PDT) Message-Id: <199810131052.DAA12263@implode.root.com> To: Eivind Eklund cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: inetd is ill? syslogd is anemic? In-reply-to: Your message of "Tue, 13 Oct 1998 12:48:45 +0200." <19981013124845.25955@follo.net> From: David Greenman Reply-To: dg@root.com Date: Tue, 13 Oct 1998 03:52:55 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> : My machine is a PPro-based box - I don't know if this matter. I seem >> : to remember it also happening after I upgraded to 80MB; I know it >> : happened when I had 64MB, at least. >> >> Mine is dual PPro 64MB as well, so this config is likely to make it >> easier to reproduce. Meanwhile, I think I'll upgrade my memory >> (as Garrett Wollman suggested) after all, and see if it goes away -- >> although like as not a kernel update and recompile will suffice. > >I've not seen any commits that should fix it, and I've been on the >lookout for them. There's a non-zero chance that the stuff I committed earlier this morning might have an effect on it. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message