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

Whitespace cleanup for the previous two revisions.

Browse source
This commit is contained in:
Christian Brueffer 2007-04-29 16:01:47 +00:00
parent 3454947c5f
commit 6998ce7d54
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=30119
1 changed files with 9 additions and 9 deletions

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

@ -4705,7 +4705,7 @@ route_hostD="192.168.173.4 hatm0 0 102 llc/snap ubr"</programlisting>
act in conjunction with a Round Robin <acronym>DNS</acronym>
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
server's <acronym>IP</acronym>s. When a failure occurs, the
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 failover server
@ -4738,17 +4738,17 @@ ifconfig_carp0="vhid 2 pass testpass 192.168.1.51/24"</programlisting>
<note>
<para>It is very important that the passwords, specified by the
<option>pass</option> option to <command>ifconfig</command>, are identical. The
<devicename>carp</devicename> devices will only listen to
and accept advertisements from machines with the correct
password. The <acronym>VHID</acronym> must also be different
for each machine.</para>
<option>pass</option> option to <command>ifconfig</command>,
are identical. The <devicename>carp</devicename> devices will
only listen to and accept advertisements from machines with the
correct password. The <acronym>VHID</acronym> must also be
different for each machine.</para>
</note>
<para>The third machine,
<hostid>provider.example.org</hostid>, should be prepared so that it may handle
failover from either host. This machine will require two
<devicename>carp</devicename> devices, one to handle each
<hostid>provider.example.org</hostid>, should be prepared so that
it may handle 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>