From owner-freebsd-stable Fri Nov 14 11:39:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25936 for stable-outgoing; Fri, 14 Nov 1997 11:39:02 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25923 for ; Fri, 14 Nov 1997 11:38:57 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id LAA08498; Fri, 14 Nov 1997 11:40:09 -0800 (PST) Message-Id: <199711141940.LAA08498@implode.root.com> To: "Jan L. Peterson" cc: "Studded" , "FreeBSD Stable List" Subject: Re: Serious problem with ipfw in 11/10 Snap In-reply-to: Your message of "Fri, 14 Nov 1997 09:56:36 MST." <199711141656.JAA29684@banana.imall.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 14 Nov 1997 11:40:09 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >The only thing we can't do remotely at the moment is powercycle the >machines. We're looking into X10 for that. :-) For wcarchive, I constructed a "remote console" machine that hooks to wcarchive's console serial port. The remote console is on the net as well, and I always have an xterm (with logging enabled) open on wcarchive's console. Additionally, I modified a cheap internal modem so that the hook relay was connected to the reset switch on wcarchive. Thus, I can reset wcarchive with a simple "atdt" on the remote console machine. I also wrote a watchdog script that pings wcarchive regularly and does an automatic reset if the machine becomes unreachable for an extended period. I've never had a need to power cycle the hardware - reset has always been sufficient and it is much less tramatic on the hardware (wcarchive fills most of a 6 foot rack). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project