os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

fail over -> failover, the latter seems to have been established more or less

Browse source 
as the standard spelling.

Reviewed by:	trhodes
This commit is contained in:
Christian Brueffer 2007-04-29 15:59:43 +00:00
parent 8ea2d4dd24
commit 3454947c5f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=30118
1 changed files with 5 additions and 5 deletions

10
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -4699,16 +4699,16 @@ route_hostD="192.168.173.4 hatm0 0 102 llc/snap ubr"</programlisting>
<title>Using CARP For Server Availability (CARP)</title>
<para>One use of <acronym>CARP</acronym>, as noted above, is for
server availability. This example will provide fail over support
server availability. This example will provide failover support
for three hosts, all with unique <acronym>IP</acronym>
addresses and providing the same web content. These machines will
act in conjunction with a Round Robin <acronym>DNS</acronym>
configuration. The fail over machine will have two additional
configuration. The failover machine will have two additional
<acronym>CARP</acronym> interfaces, one for each of the content
server's <acronym>IP</acronym>s. When a failure occurs, the
fail over server should pick up the failed machine's
failover server should pick up the failed machine's
<acronym>IP</acronym> address. This means the failure should
go completely unnoticed to the user. The fail over server
go completely unnoticed to the user. The failover server
requires identical content and services as the other content
servers it is expected to pick up load for.</para>
@ -4747,7 +4747,7 @@ ifconfig_carp0="vhid 2 pass testpass 192.168.1.51/24"</programlisting>
<para>The third machine,
<hostid>provider.example.org</hostid>, should be prepared so that it may handle
fail over from either host. This machine will require two
failover from either host. This machine will require two
<devicename>carp</devicename> devices, one to handle each
host. The appropriate <filename>rc.conf</filename>
configuration lines will be similar to the following:</para>