(fwd) Re: squid

Andrey Gerzhov (kittle@freeland.alex-ua.com)
Sun, 6 Dec 1998 14:40:02 +0200 (EET)

-- forwarded message --
Path: freeland.alex-ua.com!routki.ki.yurteh.net!carrier.kiev.ua!srcc!newsfeed.gamma.ru!Gamma.RU!ddt.demos.su!fido-news-server
From: Vadim G Zabelin <landcruiser@mailcity.com>
Newsgroups: fido7.ru.unix.bsd
Subject: Re: squid
Date: 4 Dec 1998 09:42:55 +0300
Organization: V. Zabelin Enterprises
Lines: 41
Approved: <gateway@fido7.ru>
Message-ID: <366783DF.2C75B773@mailcity.com>
References: <1164622939@minas-tirith.pol.ru> <912675260@p33.f18.n5020.z2.ftn>
Reply-To: landcruiser@mailcity.com
NNTP-Posting-Host: ddt.demos.su
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
X-Mailer: Mozilla 4.08 [en] (Win95; I)
X-BeforeModerator-Path: ppps.sgu.ru
X-BeforeModerator-NNTP-Posting-Host: ppps.sgu.ru
X-Trace: 4 Dec 1998 09:40:32 +0300, ppps.sgu.ru
Xref: freeland.alex-ua.com fido7.ru.unix.bsd:736

Ilya Kulagin wrote:

> 17 Nov 98 08:09:44, Alex Povolotsky wrote to hix@adm.com.ua:
> AP> squid 2.0 умеет такую фичу, как delay_pools. В FAQе есть.
> В этом FAQ, к сожалению, написано весьма темно и скудно. То, что описано в
> sample config, мне ясности тоже не добавило...
>
> Кто бы из работавших с этим чудом истолковал алгоритм или же дал ссылку на
> место, где он внятно изложен...

Если не ленится и сайте сквида поискать - то можно до первоисточников дойти
на
http://squid.nlanr.net/Squid/1.1/patches.html
первоисточник :

DELAY_HACK patch
This patch from David Luyer gives Squid the ability to control the amount
of traffic...
for all items matching one ACL delay_child_access on the basis of a
single combined pool
for all items matching the ACL delay_access on the basis of
a combined pool
a per-8-bit-net pool
a per-host pool
These are currently based on the assumption that if the last 16-bits
of an IP are unique, it's the same pool. easy
enough to fix.

Each neighbour can be tagged as ``no-delay'' if fetches from it shouldn't
be delayed. neighbours or parents without this
tag are delayed/slowed based on avaliable traffic in the ``pool,'' which
is configured with an upper limit and a per-second
feed. there's a cachemgr interface to examine all the delay pools and so
on.

И еще про это

http://www.cineca.it/proxy/search/html/9808/442.html

-- end of forwarded message --

-- 
С тем, что не помешает никогда,
                                               Kittle