Date: Sat, 08 Jul 2000 06:36:00 -0400 From: "William E. Reid" <wer@cstone.net> To: "Sean J. Schluntz" <schluntz@workofstone.com> Cc: Jason Fesler <jfesler@gigo.com>, Luigi Rizzo <luigi@info.iet.unipi.it>, Chris Shenton <cshenton@uucom.com>, Alan Batie <batie@rdrop.com>, isp@FreeBSD.ORG, Gabriel Ambuehl <gabriel_ambuehl@buz.ch> Subject: Re: load balancing Message-ID: <39670410.805908E3@cstone.net> References: <200007071934.MAA26620@mail.workofstone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I would cross connect a console between the two computers for matters like these. As long as one is up you can gain access through the console on the other, That way if it has comeup in singlie user mode or is caught running fsck you can have total access without using anything but the console. I learned that from Adrian. -=Bill schluntz@timberwolf.workofstone.net wrote: > >> If the box is faulty but still pingable with the IP alias, > >> log into the box, shutdown the alias. Next, turn the alias > >> on, on the other box. > > > >What if it's pingable, but ssh failed? And how do you solve the > >problems of needing root access to kill the alias? I don't want to > >supply an attacker with the root passwords for the another box if he > >cracks one of a pair... RSA authentication isn't better for that > >matter. > > I have a friend who solved that with an X10 kit. If his servers can't be > contacted through ssh then he just turns off the power to it so another > can take over the IP. It stays off until he has a change to go in and fix > it. (Or he can choose to power it back on remotely and see if it comes > back up correctly.) > > -Sean > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39670410.805908E3>