From owner-freebsd-chat Fri Apr 6 7:47:31 2001 Delivered-To: freebsd-chat@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 712C137B43E; Fri, 6 Apr 2001 07:47:29 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id JAA64309; Fri, 6 Apr 2001 09:47:20 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 6 Apr 2001 09:47:19 -0500 (CDT) From: Chris Dillon To: Brett Glass Cc: John Baldwin , Johann Visagie , , Dag-Erling Smorgrav Subject: Re: corporate announcement In-Reply-To: <4.3.2.7.2.20010406015339.0444f100@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 6 Apr 2001, Brett Glass wrote: > At 06:42 PM 4/5/2001, Chris Dillon wrote: > > >I don't think a watchdog would help you out in that situation anyway. > > It could. You could say, "If I don't connect in 5 minutes, flush > all the firewall rules, fall back to a minimal set of daemons, and > reboot." Yup. You wouldn't need hardware to do that, though. I could hack up a shell script to do that. I have, actually, on an old server with an lnc NIC that likes to go dead occasionally. It'll '/sbin/shutdown -r now' when it can't communicate with the outside world for a while. Not exactly the same, but it wouldn't be hard to replace the shutdown with an ipfw flush and a new ruleset in there, and to make sure certain daemons are running such as sshd. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message