From owner-freebsd-stable Wed Sep 29 1:17:22 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 9759E15064; Wed, 29 Sep 1999 01:17:04 -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 LAA02497; Wed, 29 Sep 1999 11:16:37 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Wed, 29 Sep 1999 11:16:36 +0300 (EEST) From: Adrian Penisoara To: "Jordan K. Hubbard" Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: -stable (in)stability (was Re: Best version of FBSD for INN ?) In-Reply-To: <25158.938562446@localhost> 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, On Tue, 28 Sep 1999, Jordan K. Hubbard wrote: > I'd suggest trying a 3.3-stable snapshot, just as soon as I can > get those rolling off of releng3.freebsd.org again. If it still > occurs, we're now at least debugging the latest and greatest. Isn't -STABLE tracking OK ? Unfortunately I don't think I can afford reinstalling a new release (this is a production server). Do you think the installation got somehow trashed during these succesive updates (with 'make [build|install]world') ? I've been thinking about remote attacks too (there are no user shells), could this be a cause ? BTW, this morning my co-workers caught another freeze; luckily I left a top running on a VTY; they told me that the majority of the processes were in the "idle" STATE -- strange, I haven't seen this in top until now. Could this be a hint ? > > - Jordan > Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message