From owner-freebsd-hackers Mon Oct 11 12:26:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by hub.freebsd.org (Postfix) with ESMTP id 51F4514C4A for ; Mon, 11 Oct 1999 12:26:17 -0700 (PDT) (envelope-from cmsedore@mailbox.syr.edu) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.F79F6CD0@mailer.syr.edu>; Mon, 11 Oct 1999 15:26:19 -0400 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id PAA05228; Mon, 11 Oct 1999 15:26:16 -0400 (EDT) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Mon, 11 Oct 1999 15:26:16 -0400 (EDT) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu To: Chris Costello Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine In-Reply-To: <19991011135728.F19110@holly.calldei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Oct 1999, Chris Costello wrote: > On Mon, Oct 11, 1999, Chad David wrote: > > Some replys indicated that I should use -current > > for aio_*. Would this be true also for any > > serious threading? Is -current ready for a > > semi-production environment? > > Not really. The fact is that a user program can crash > 3.3-STABLE and that is unacceptable. No user program should be > able to bring down a system, _especially_ in -STABLE. You need to rip out most of aio_* in -stable or -current for this to be true. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message