From: hno <>
Date: Sat, 22 Feb 2003 04:01:16 +0000 (+0000)
Subject: Document the 'carp' cache_peer option
X-Git-Tag: SQUID_3_0_PRE1~320
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d3d91b36837bae83432c7b2e1289d1326d119449;p=thirdparty%2Fsquid.git

Document the 'carp' cache_peer option
---

diff --git a/src/cf.data.pre b/src/cf.data.pre
index 192779044e..d9d57f4c35 100644
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -1,6 +1,6 @@
 
 #
-# $Id: cf.data.pre,v 1.304 2003/02/21 19:53:01 hno Exp $
+# $Id: cf.data.pre,v 1.305 2003/02/21 21:01:16 hno Exp $
 #
 #
 # SQUID Web Proxy Cache          http://www.squid-cache.org/
@@ -388,6 +388,7 @@ DOC_START
 		     default
 		     round-robin
 		     weighted-round-robin
+		     carp
 		     multicast-responder
 		     closest-only
 		     no-digest
@@ -452,6 +453,11 @@ DOC_START
 		     time. Closer parents are used more often. 
 		     Usually used for background-ping parents.
 
+		     use 'carp' to define a set of parents which should
+		     be used as a CARP array. The requests will then be
+		     distributed among the parents based on the CARP load
+		     balancing hash function based on their weigth.
+
 		     'multicast-responder' indicates that the named peer
 		     is a member of a multicast group.  ICP queries will
 		     not be sent directly to the peer, but ICP replies