From owner-freebsd-isp Thu Oct 3 11:16:57 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA12465 for isp-outgoing; Thu, 3 Oct 1996 11:16:57 -0700 (PDT) Received: from pegasus.com (pegasus.com [140.174.243.13]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA12458 for ; Thu, 3 Oct 1996 11:16:51 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id IAA13726; Thu, 3 Oct 1996 08:14:46 -1001 Date: Thu, 3 Oct 1996 08:14:46 -1001 From: richard@pegasus.com (Richard Foulk) Message-Id: <199610031815.IAA13726@pegasus.com> In-Reply-To: Joe Greco "Re: RAID Controller Product" (Oct 3, 11:26am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Joe Greco , jeff@mercury.jorsm.com (Jeff.Lynch-JORSM.Internet) Subject: Re: RAID Controller Product Cc: freebsd-isp@FreeBSD.ORG 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. Hadn't thought of that. In that light, more reliable servers (with RAID, etc.) may be more appropriate than multiple/redundant servers (since that's where this thread started.) Richard