From owner-freebsd-stable Thu Mar 16 22:11:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 116BC37B578 for ; Thu, 16 Mar 2000 22:11:47 -0800 (PST) (envelope-from sewall@ix.netcom.com) Received: from ix.netcom.com (sji-ca13-155.ix.netcom.com [209.109.238.155]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id BAA04747; Fri, 17 Mar 2000 01:11:43 -0500 (EST) Message-ID: <38D1CC73.7E5524C1@ix.netcom.com> Date: Thu, 16 Mar 2000 22:11:00 -0800 From: "Scott R. Sewall" Organization: Rosetta software X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Michael Robinson Cc: freebsd-stable@freebsd.org Subject: Re: How to force remote reboot of 3.4-Release? References: <200003170213.KAA26062@netrinsics.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I use neptune to generate SYN flood. Don't remember the download site. -- Scott Michael Robinson wrote: > Last night, I was running a very large Postgresql query on one of my > colocated development servers when all of a sudden the session completely > froze. Since then, I can get TCP connections to all the open ports, but > they just hang with no services ever coming up. Ping works fine. > > I assume this is due to one of FreeBSD's resource starvation features. > What I'd like to know is, once the server gets into this state, is it > possible to exploit any of the other resource starvation features in > 3.4-Release to force a reboot? Getting access to the server is a big > pain in the rear, so I'd like to avoid the trip if at all possible. > > Would a SYN flood do it? If so, does anyone know of a good SYN flood tool? > > -Michael Robinson > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message