From owner-freebsd-stable Wed Feb 14 8: 2:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from diskfarm.firehouse.net (rdu26-60-051.nc.rr.com [66.26.60.51]) by hub.freebsd.org (Postfix) with ESMTP id 8154437B401 for ; Wed, 14 Feb 2001 08:02:07 -0800 (PST) Received: (from abc@localhost) by diskfarm.firehouse.net (8.11.1/8.11.1) id f1EG1Fm75149; Wed, 14 Feb 2001 11:01:15 -0500 (EST) (envelope-from abc) Date: Wed, 14 Feb 2001 11:01:15 -0500 From: Alan Clegg To: Drew Sanford Cc: Terry Rossi , Michael DeMutis , freebsd-stable@FreeBSD.ORG Subject: Re: Named crashing Message-ID: <20010214110115.J72602@diskfarm.firehouse.net> References: <3A8AA108.7050007@bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <3A8AA108.7050007@bellsouth.net>; from lauasanf@bellsouth.net on Wed, Feb 14, 2001 at 09:15:20AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unless the network is lying to me again, Drew Sanford said: > > Just to add to the mix this happened to me two days ago on my > 4.0-Release box - I've been meaning to upgrade it, but upgrading this > particular box is a real pain. I'd love to know what everyone comes up with. Can I place a guess in the pool that says that someone is working on an exploit that at this point only kills the server? AlanC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message