From owner-freebsd-current Wed Dec 9 17:24:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29030 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:24:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29022 for ; Wed, 9 Dec 1998 17:24:56 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id UAA159242; Wed, 9 Dec 1998 20:25:33 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199812092149.NAA51668@rah.star-gate.com> References: Your message of "Wed, 09 Dec 1998 13:14:43 PST." Date: Wed, 9 Dec 1998 20:24:50 -0500 To: Amancio Hasty , Marc Slemko From: Garance A Drosihn Subject: Re: Current ready for prime time web server ? Cc: Mike Tancsa , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:49 PM -0800 12/9/98, Amancio Hasty wrote: > May ask why do you think that 3.0 is not ready for prime time? Isn't true that -- *by definition* -- the freebsd-current tree is not *recommended* for production servers? Not now, not ever? Marc merely said that that he would not really recommend using -current for production servers right now. He isn't necessarily casting aspersions on 3.0. I assumed that he was just stating the official freebsd position. Now, there are things in current which could be very nice to have on a web server, including a production web server. I do use an earlier snapshot of 3.0 for a production (non-web) server I have, for instance. But for the problem as described, it does seem that simply recompiling apache was the best recommendation. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message