From owner-freebsd-isp Thu Oct 3 09:28:01 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA06595 for isp-outgoing; Thu, 3 Oct 1996 09:28:01 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA06575 for ; Thu, 3 Oct 1996 09:27:59 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA06978; Thu, 3 Oct 1996 11:26:49 -0500 From: Joe Greco Message-Id: <199610031626.LAA06978@brasil.moneng.mei.com> Subject: Re: RAID Controller Product To: jeff@mercury.jorsm.com (Jeff.Lynch-JORSM.Internet) Date: Thu, 3 Oct 1996 11:26:48 -0500 (CDT) Cc: richard@pegasus.com, freebsd-isp@FreeBSD.ORG In-Reply-To: from "Jeff.Lynch-JORSM.Internet" at Oct 3, 96 09:22:21 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Wed, 2 Oct 1996, Richard Foulk wrote: > > A quick alias addition could fix that. One box could check periodically > > to see that another is still up, when it stops responding you take over > > for its IP address too. > > > > > > Richard > > This looks like the closest thing to a perfect solution. After > human intervention on the dead machine, you just delete the > alias on the backup news server! Not sure, but you also might > need to modify the arp tables on all the locally connected machines > though for a smooth transition. The other non-obvious downside to this is that the reason you are doing it in the first place is so that newsreaders can connect. However once connected they like to stay connected for a long time... and when you bring the other machine back online, you are going to have a SECOND service disruption. Eccch. ... JG