From owner-freebsd-stable Thu Mar 16 18:12:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id B470137BD7F for ; Thu, 16 Mar 2000 18:12:48 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com (robinson@fw-24-151-a8.bta.net.cn [202.108.24.151]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id KAA23067 for ; Fri, 17 Mar 2000 10:10:49 +0800 (GMT) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.9.3) id KAA26062 for freebsd-stable@freebsd.org; Fri, 17 Mar 2000 10:13:41 +0800 (+0800) (envelope-from robinson) Date: Fri, 17 Mar 2000 10:13:41 +0800 (+0800) From: Michael Robinson Message-Id: <200003170213.KAA26062@netrinsics.com> To: freebsd-stable@freebsd.org Subject: How to force remote reboot of 3.4-Release? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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