From owner-freebsd-chat Wed Jul 23 12:19:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA08316 for chat-outgoing; Wed, 23 Jul 1997 12:19:10 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08295; Wed, 23 Jul 1997 12:19:04 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id MAA08413; Wed, 23 Jul 1997 12:18:59 -0700 (PDT) Date: Wed, 23 Jul 1997 12:18:58 -0700 (PDT) From: Jaye Mathisen To: The Classiest Man Alive cc: chat@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: -current report. :) (moved to chat/questions) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I really can't say. Other people use FreeBSD just fine for their newsserver, and I did too, but I would get these random fs-related crashes. John Dyson looked at them, and said "yep, looks like some vnode locking problems", and patched up 3.0 (as far as I can tell). However, the patches never made it into 2.2.2. I was able to reproduce it on 2 different machines. I would still use 2.2.2 and get the adaptec fixes, you should be fine, and certainly plenty of people are using FreeBSD for newsserver just fine. Must've just been my combo... On Wed, 23 Jul 1997, The Classiest Man Alive wrote: > On Wed, 23 Jul 1997, Jaye Mathisen wrote: > > : Well, I took the plunge, and upgraded my crash-ridden 2.2.2 INN newsserver > : to 3.0-current as of 7/19, and it's been solid as the proverbial rock > : for a few days now. > > Okay, see, now you've got me worried. What crashes? I convinced my IS > manager to let me set up our news server with FreeBSD rather than NT. I'm > using 2.2.1, but I read that 2.2.2 fixes some problems with using an > Adaptec 2940 under a heavy load, so I thought I'd upgrade to the latest > release. And now you tell me this? > > So, from your experience, should I upgrade to 2.2.2 or should I stick it > out with 2.2.1? I don't think 3.0-current is much of an option for me. > > K.S. > >