From owner-freebsd-stable Sun Sep 26 4:31: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id D8B6D15180 for ; Sun, 26 Sep 1999 04:31:00 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id OAA14309; Sun, 26 Sep 1999 14:30:29 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Sun, 26 Sep 1999 14:30:29 +0300 (EEST) From: Adrian Penisoara To: The Hermit Hacker Cc: freebsd-stable@FreeBSD.ORG Subject: Re: -stable (in)stability (was Re: Best version of FBSD for INN ?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, On Sat, 25 Sep 1999, Adrian Penisoara wrote: > On Sat, 25 Sep 1999, The Hermit Hacker wrote: > > > > > Just to confirm...I've had similar problems, but *only* after moving to > > INN-CURRENT, which makes *very* heavy use of MMAP() :( > > > > What version of INN are you running? > > I'm not running any kind of INN -- but lately I have been playing with > nntpcached (2.3.3), but the problems have been manifesting even before > installing it... Hey, this is interesting: I have another server right next to the faulty one wich is SMP and doesn't exhibit lockups; they're usually synced in terms of -stable source tracking. I'll try to compare the two systems in terms of packages and optional services that are running, although the second system is very lightly loaded and this could hide the problem... Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message