date:20090303

SQUID_MAXFD <-- what this is mean ? and how much the default and
recommended number

-- 
-=-=-=-=
Personal Blog http://my.blog.or.id ( lagi belajar )
Hot News !!! : Pengin punya Layanan SMS PREMIUM ? Contact me ASAP.
dapatkan Share revenue MAXIMAL tanpa syarat traffic...

Re: [squid-users] squidaio_queue_request: WARNING - Queue congestion

2009-03-03 Thread Shekhar Gupta

it's showing

client_http.requests = 102.190863/sec

On Wed, Mar 4, 2009 at 1:53 AM, Chris Robertson  wrote:
> Shekhar Gupta wrote:
>>
>> can you please tell me how to find hit/sec .
>
> squidclient mgr:utilization
>
> Chris
>

[squid-users] url_rewrite_program

2009-03-03 Thread Ruwan Janapriya

I have written a perl script and used as a url_rewrite_program in
squid v2.7. It worked fine until I upgraded it to v3.0. Now I am
getting a access denied error. It never cache the images I asked it to
cache. Do I have to make any changes to the configuration for v3.0?

Furthermore, I want to manipulate HTTP headers. What is the best
method I should follow? I saw ICAP could help me to do that? however I
couldn't find a good ICAP server implementation for windows. I
upgraded to v3.0, since I read in several users comments that v2.X
series does not support ICAP well.

thanks in advance,

J

Re: [squid-users] Squid & url rewriter


Amos Jeffries wrote:

echo and print in PHP and perl IIRC operate slightly differently.

I have found echo "blah\n"; flush(); both to be needed for PHP for 
timely results.


The earlier mail was about perl print having an implicit \n already. 
echo in PHP does not.


Amos


Whoops.  The difference in the two scripts is the Perl one was rewriting 
the string passed to it (which already had a newline at the end) and the 
PHP script was outputting a completely new string.  The PHP script 
should probably look like:


#!/usr/bin/php
 
 echo "302:http://www.yahoo.fr/\n";;

 flush;

}
?>

Chris

Re: [squid-users] delaypolls

ok

ty

On Wed, Mar 4, 2009 at 8:18 AM, Amos Jeffries  wrote:
> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> so the correct syntax is :
>>
>> delay_pools 2
>> delay_class 1 1
>> delay_parameters 1 32000/64000
>> delay_access 1 allow domain-nakal !free
>> delay_access 1 allow nakal  !free
>> delay_access 1 deny ALL
>>
>> delay_class 2 2
>> delay_parameters 2 1000/1000 1000/2800
>> delay_access 2 allow porn !free
>> delay_access 2 deny ALL
>>
>>
>> this one ?
>
> I think so yes.
>
> Amos
> - Show quoted text -
>
>>
>> On Wed, Mar 4, 2009 at 7:19 AM, Amos Jeffries 
>> wrote:
>>>
>>> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

 so the correct syntax is :

 delay_pools 2
 delay_class 1 1
 delay_parameters 1 32000/64000
 delay_access 1 allow domain-nakal !free
 delay_access 1 allow nakal  !free
 delay_access 1 deny ALL

 delay_class 2 1
 delay_parameters 2 1000/1000 1000/2800
 delay_access 2 allow porn !free
 delay_access 2 deny ALL



 about class 2 is correct ?
>>>
>>> Ah, sorry I overlooked, you have two class-1 pools defined.
>>> http://www.squid-cache.org/Doc/config/delay_class/
>>>
>>> so...
>>>  delay_parameters 2 1000/1000
>>> or
>>>  delay_parameters 2 1000/2800
>>> or
>>>  delay_class 2 2
>>>  delay_parameters 2 1000/1000 1000/2800
>>>
>>> Amos
>>> - Show quoted text -
>>>
 On Fri, Feb 27, 2009 at 3:53 PM, Amos Jeffries 
 wrote:
>
> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> can you fix it for me ?
>>
>> i want user access class 1 got 32000 but they can burst to 64000
>>
> Just change the "a/b" parts as you need.
> The numbers are /  and count bytes.
>
> Amos
> - Show quoted text -
>
>> and when class 2 same thing but with lower b/w
>>
>> On Fri, Feb 27, 2009 at 3:36 PM, Amos Jeffries 
>> wrote:
>>>
>>> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

 delay_parameters 1 32000/32000 2500/64000
>>>
>>> (class 1) All people assigned into this pool share a single 32000
>>> byte
>>> per
>>> second pipe.
>>>
>>> The other parameters 250/64000 is garbage, since a class 1 pool only
>>> has
>>> one
>>> set of speed parameters.
>>>
 and
 delay_parameters 2 1000/1000 1000/2800
>>>
>>> (class 2) people assigned into this pool all share a 1000 byte per
>>> second
>>> pipe.
>>> Individual people start off with 2800 (or maybe only 1000) bytes, but
>>> are
>>> limited to 1000 per second once they start downloading.
>>>
>>> I'm not sure what Squid does when one IP is allowed a higher starting
>>> bytes
>>> than the entire group, its probably not good.
>>>
 On Fri, Feb 27, 2009 at 2:36 PM, Amos Jeffries
 
 wrote:
>
> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> what is this paramenter mean ?
>>
>> acl domain-nakal url_regex -i "/etc/squid/domain-nakal.txt"
>> acl nakal url_regex -i "/etc/squid/ext-nakal.txt"
>> acl porn url_regex -i "/etc/squid/porn.txt"
>>
>> delay_pools 2
>> delay_class 1 1
>> delay_parameters 1 32000/32000 2500/64000
>> delay_access 1 allow domain-nakal !free
>> delay_access 1 allow nakal  !free
>> delay_access 1 deny ALL
>>
>> delay_class 2 1
>> delay_parameters 2 1000/1000 1000/2800
>> delay_access 2 allow porn !free
>> delay_access 2 deny ALL
>>
>>
>> please tell me in english
>>
> Which one? you list many,many parameters.
>
>>> Amos
>>> --
>>> Please be using
>>>  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>>>  Current Beta Squid 3.1.0.6
>>>
>>
>>
>>
>
>
> --
> Please be using
>  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>  Current Beta Squid 3.1.0.6
>



-- 
-=-=-=-=
Personal Blog http://my.blog.or.id ( lagi belajar )
Hot News !!! : Pengin punya Layanan SMS PREMIUM ? Contact me ASAP.
dapatkan Share revenue MAXIMAL tanpa syarat traffic...

Re: [squid-users] delaypolls


░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

so the correct syntax is :

delay_pools 2
delay_class 1 1
delay_parameters 1 32000/64000
delay_access 1 allow domain-nakal !free
delay_access 1 allow nakal  !free
delay_access 1 deny ALL

delay_class 2 2
delay_parameters 2 1000/1000 1000/2800
delay_access 2 allow porn !free
delay_access 2 deny ALL


this one ?


I think so yes.

Amos



On Wed, Mar 4, 2009 at 7:19 AM, Amos Jeffries  wrote:

░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

so the correct syntax is :

delay_pools 2
delay_class 1 1
delay_parameters 1 32000/64000
delay_access 1 allow domain-nakal !free
delay_access 1 allow nakal  !free
delay_access 1 deny ALL

delay_class 2 1
delay_parameters 2 1000/1000 1000/2800
delay_access 2 allow porn !free
delay_access 2 deny ALL



about class 2 is correct ?

Ah, sorry I overlooked, you have two class-1 pools defined.
http://www.squid-cache.org/Doc/config/delay_class/

so...
 delay_parameters 2 1000/1000
or
 delay_parameters 2 1000/2800
or
 delay_class 2 2
 delay_parameters 2 1000/1000 1000/2800

Amos
- Show quoted text -


On Fri, Feb 27, 2009 at 3:53 PM, Amos Jeffries 
wrote:

░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

can you fix it for me ?

i want user access class 1 got 32000 but they can burst to 64000


Just change the "a/b" parts as you need.
The numbers are /  and count bytes.

Amos
- Show quoted text -


and when class 2 same thing but with lower b/w

On Fri, Feb 27, 2009 at 3:36 PM, Amos Jeffries 
wrote:

░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

delay_parameters 1 32000/32000 2500/64000

(class 1) All people assigned into this pool share a single 32000 byte
per
second pipe.

The other parameters 250/64000 is garbage, since a class 1 pool only
has
one
set of speed parameters.


and
delay_parameters 2 1000/1000 1000/2800

(class 2) people assigned into this pool all share a 1000 byte per
second
pipe.
Individual people start off with 2800 (or maybe only 1000) bytes, but
are
limited to 1000 per second once they start downloading.

I'm not sure what Squid does when one IP is allowed a higher starting
bytes
than the entire group, its probably not good.


On Fri, Feb 27, 2009 at 2:36 PM, Amos Jeffries 
wrote:

░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

what is this paramenter mean ?

acl domain-nakal url_regex -i "/etc/squid/domain-nakal.txt"
acl nakal url_regex -i "/etc/squid/ext-nakal.txt"
acl porn url_regex -i "/etc/squid/porn.txt"

delay_pools 2
delay_class 1 1
delay_parameters 1 32000/32000 2500/64000
delay_access 1 allow domain-nakal !free
delay_access 1 allow nakal  !free
delay_access 1 deny ALL

delay_class 2 1
delay_parameters 2 1000/1000 1000/2800
delay_access 2 allow porn !free
delay_access 2 deny ALL


please tell me in english


Which one? you list many,many parameters.


Amos
--
Please be using
 Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
 Current Beta Squid 3.1.0.6








--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
  Current Beta Squid 3.1.0.6

Re: [squid-users] delaypolls

so the correct syntax is :

delay_pools 2
delay_class 1 1
delay_parameters 1 32000/64000
delay_access 1 allow domain-nakal !free
delay_access 1 allow nakal  !free
delay_access 1 deny ALL

delay_class 2 2
delay_parameters 2 1000/1000 1000/2800
delay_access 2 allow porn !free
delay_access 2 deny ALL


this one ?

On Wed, Mar 4, 2009 at 7:19 AM, Amos Jeffries  wrote:
> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> so the correct syntax is :
>>
>> delay_pools 2
>> delay_class 1 1
>> delay_parameters 1 32000/64000
>> delay_access 1 allow domain-nakal !free
>> delay_access 1 allow nakal  !free
>> delay_access 1 deny ALL
>>
>> delay_class 2 1
>> delay_parameters 2 1000/1000 1000/2800
>> delay_access 2 allow porn !free
>> delay_access 2 deny ALL
>>
>>
>>
>> about class 2 is correct ?
>
> Ah, sorry I overlooked, you have two class-1 pools defined.
> http://www.squid-cache.org/Doc/config/delay_class/
>
> so...
>  delay_parameters 2 1000/1000
> or
>  delay_parameters 2 1000/2800
> or
>  delay_class 2 2
>  delay_parameters 2 1000/1000 1000/2800
>
> Amos
> - Show quoted text -
>
>>
>> On Fri, Feb 27, 2009 at 3:53 PM, Amos Jeffries 
>> wrote:
>>>
>>> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

 can you fix it for me ?

 i want user access class 1 got 32000 but they can burst to 64000

>>> Just change the "a/b" parts as you need.
>>> The numbers are /  and count bytes.
>>>
>>> Amos
>>> - Show quoted text -
>>>
 and when class 2 same thing but with lower b/w

 On Fri, Feb 27, 2009 at 3:36 PM, Amos Jeffries 
 wrote:
>
> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> delay_parameters 1 32000/32000 2500/64000
>
> (class 1) All people assigned into this pool share a single 32000 byte
> per
> second pipe.
>
> The other parameters 250/64000 is garbage, since a class 1 pool only
> has
> one
> set of speed parameters.
>
>> and
>> delay_parameters 2 1000/1000 1000/2800
>
> (class 2) people assigned into this pool all share a 1000 byte per
> second
> pipe.
> Individual people start off with 2800 (or maybe only 1000) bytes, but
> are
> limited to 1000 per second once they start downloading.
>
> I'm not sure what Squid does when one IP is allowed a higher starting
> bytes
> than the entire group, its probably not good.
>
>> On Fri, Feb 27, 2009 at 2:36 PM, Amos Jeffries 
>> wrote:
>>>
>>> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

 what is this paramenter mean ?

 acl domain-nakal url_regex -i "/etc/squid/domain-nakal.txt"
 acl nakal url_regex -i "/etc/squid/ext-nakal.txt"
 acl porn url_regex -i "/etc/squid/porn.txt"

 delay_pools 2
 delay_class 1 1
 delay_parameters 1 32000/32000 2500/64000
 delay_access 1 allow domain-nakal !free
 delay_access 1 allow nakal  !free
 delay_access 1 deny ALL

 delay_class 2 1
 delay_parameters 2 1000/1000 1000/2800
 delay_access 2 allow porn !free
 delay_access 2 deny ALL


 please tell me in english

>>> Which one? you list many,many parameters.
>>>
>
> Amos
> --
> Please be using
>  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>  Current Beta Squid 3.1.0.6
>



-- 
-=-=-=-=
Personal Blog http://my.blog.or.id ( lagi belajar )
Hot News !!! : Pengin punya Layanan SMS PREMIUM ? Contact me ASAP.
dapatkan Share revenue MAXIMAL tanpa syarat traffic...

Re: [squid-users] squid and ftp


shailesh shinde wrote:

why does squid not support ftp ,smtp like protocols on the client side.
Is it possible to write modules for such a support ?


Squid is an HTTP proxy. It converts FTP into HTTP. That is the only 
support it has for such non-HTTP protocols.


It's possible to write such modules, but not part of what Squid does. 
There are other software called FTP proxies and such for that.




If yes what would be the feasibility of the work because we are a
group of 3 third year computer engineering students willing to do our
final year project on squid.


If you are just looking for a project to do there are a number of things 
that need to be done. All listed on the RoadMap

 http://wiki.squid-cache.org/RoadMap/Squid3

I'd suggest taking on one of the features from Squid-2.7 which need to 
be ported to 3.0. The code already exists in 2.7 for an idea of how to 
do it, but most need a full re-write and re-test to work in Squid-3.

  http://www.squid-cache.org/Versions/v3/3.1/RELEASENOTES.html#s7
The authenticate short-circuit, broken vary, external_acl_type ACL/DATA 
tags, or max_filedescriptors are all open for people wanting to give it 
a shot.


Please get into contact with the squid-...@squid-cache.org mailing list 
for further contact on this or more ideas about things to do.


Cheers
Amos
--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
  Current Beta Squid 3.1.0.6

RE: [squid-users] Streaming is killing Squid cache

2009-03-03 Thread Brett Glass


At 02:48 PM 3/1/2009, Gregori Parker wrote:


Better yet, implement a wsus server,


No can do. You have to configure every computer on the network to 
use it, and you must be an institutional user of Windows with 
Windows servers. (We will never use any version of Windows as a 
server if there's any way we can help it.)


--Brett Glass

Re: [squid-users] delaypolls


░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

so the correct syntax is :

delay_pools 2
delay_class 1 1
delay_parameters 1 32000/64000
delay_access 1 allow domain-nakal !free
delay_access 1 allow nakal  !free
delay_access 1 deny ALL

delay_class 2 1
delay_parameters 2 1000/1000 1000/2800
delay_access 2 allow porn !free
delay_access 2 deny ALL



about class 2 is correct ?


Ah, sorry I overlooked, you have two class-1 pools defined.
http://www.squid-cache.org/Doc/config/delay_class/

so...
  delay_parameters 2 1000/1000
or
  delay_parameters 2 1000/2800
or
  delay_class 2 2
  delay_parameters 2 1000/1000 1000/2800

Amos



On Fri, Feb 27, 2009 at 3:53 PM, Amos Jeffries  wrote:

░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

can you fix it for me ?

i want user access class 1 got 32000 but they can burst to 64000


Just change the "a/b" parts as you need.
The numbers are /  and count bytes.

Amos
- Show quoted text -


and when class 2 same thing but with lower b/w

On Fri, Feb 27, 2009 at 3:36 PM, Amos Jeffries 
wrote:

░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

delay_parameters 1 32000/32000 2500/64000

(class 1) All people assigned into this pool share a single 32000 byte
per
second pipe.

The other parameters 250/64000 is garbage, since a class 1 pool only has
one
set of speed parameters.


and
delay_parameters 2 1000/1000 1000/2800

(class 2) people assigned into this pool all share a 1000 byte per second
pipe.
Individual people start off with 2800 (or maybe only 1000) bytes, but are
limited to 1000 per second once they start downloading.

I'm not sure what Squid does when one IP is allowed a higher starting
bytes
than the entire group, its probably not good.


On Fri, Feb 27, 2009 at 2:36 PM, Amos Jeffries 
wrote:

░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

what is this paramenter mean ?

acl domain-nakal url_regex -i "/etc/squid/domain-nakal.txt"
acl nakal url_regex -i "/etc/squid/ext-nakal.txt"
acl porn url_regex -i "/etc/squid/porn.txt"

delay_pools 2
delay_class 1 1
delay_parameters 1 32000/32000 2500/64000
delay_access 1 allow domain-nakal !free
delay_access 1 allow nakal  !free
delay_access 1 deny ALL

delay_class 2 1
delay_parameters 2 1000/1000 1000/2800
delay_access 2 allow porn !free
delay_access 2 deny ALL


please tell me in english


Which one? you list many,many parameters.



Amos
--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
  Current Beta Squid 3.1.0.6

Re: [squid-users] Problem with Reverse Proxy and multiple domains


Chris Robertson wrote:

Drew Wrobel wrote:
I made the changes you suggested, but I started getting the following 
error messages in the log:


123456.com w.x.y.z - - [03/Mar/2009:12:09:45 -0500] "GET 
http://123456.com/ HTTP/1.1" 403 1379 "-" "Mozilla/4.0 (compatible; 
MSIE 7.0; Windows NT 5.1; GTB5; .NET CLR 1.0.3705; .NET CLR 1.1.4322; 
Media Center PC 4.0)" TCP_DENIED:NONE


When I went to the web site and I get the squid ERR_ACCESS_DENIED page 
instead.


Here are the new lines that I had put in as you suggested.  Not sure 
if I over did it with the http_access lines.


Had one question thought.  Since the web-server is handling both 
www.123456.com and 123456.com, is the first acl valid

for both?

I also took out the entries for abcdev and 987zyx and still doesn't 
work.  What am I missing/doing wrong.



http_port 80 accel vhost

acl 123456 dstdomain 123456.com
acl abcdef dstdomain abcdef.com
acl 987zyx dstdomain 987zyx.com
  


All three of the domains should be preceded by a period.  Replace these 
with...


acl 123456 dstdomain .123456.com
acl abccdef dstdomain .abcdef.com
acl 987zyx dstdomain .987zyx.com



cache_peer_access 192.168.2.10 allow 123456
cache_peer_access 192.168.2.10 allow abcdef
cache_peer_access 192.168.2.10 allow 987zyx
cache_peer_access 192.168.2.10 deny all
  


So does the host 192.168.2.10 contain the data for all three domains?  
You  might want to read 
http://wiki.squid-cache.org/ConfigExamples/Reverse/MultipleWebservers if 
not.  If it does, read and follow 
http://wiki.squid-cache.org/ConfigExamples/Reverse/VirtualHosting first, 
then add the redundant peers.



http_access allow 123456
http_access allow abcdef
http_access allow 987zyx


cache_peer_access 192.168.2.11 allow 123456
cache_peer_access 192.168.2.11 allow abcdef
cache_peer_access 192.168.2.11 allow 987zyx
cache_peer_access 192.168.2.11 deny all
  


Same question here.


http_access allow 123456
http_access allow abcdef
http_access allow 987zyx
  


These three lines are redundant, as http_access for these domains has 
already been allowed.




cache_peer_access 192.168.2.12 allow 123456
cache_peer_access 192.168.2.12 allow abcdef
cache_peer_access 192.168.2.12 allow 987zyx
cache_peer_access 192.168.2.12 deny all
http_access allow 123456
http_access allow abcdef
http_access allow 987zyx

http_access deny all
never_direct allow all


Um.  I don't think you want never_direct in a acceleration setup, unless 
you are setting it up in a weird way.


It's redundant. Just there for clarity of what going on.

Amos
--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
  Current Beta Squid 3.1.0.6

Re: [squid-users] Squid and NTLM Authentication


Ryan McCain wrote:

On Mon, Mar 2, 2009 at  5:36 PM, in message

, "Amos
Jeffries"  wrote: 

 We are using squid-2.5.STABLE12-18.12


Please use a newer more capable Squid.  There have been MANY improvements
since 2.5 was made obsolete.

Amos



The only reason we are using  that version is because it's the latest version 
supported w/ SLES 10.   Does this version or a newer version support the 
scenario I described?

Thanks..



Ah SLES. They have actually managed to be slower than RedHat on updating 
their software.


Okay, from what I can tell you're pretty much screwed. Unless you are a 
guru with package building and installing on SLES, or willing to change OS.
The faster solution may be to check and change the authentication type 
required by IIS.


For the record, yes the latest 2.6 and 2.7 support pass-thru for NTLM 
and kerberos negotiation, one of which I believe is causing your problem.


Amos
--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
  Current Beta Squid 3.1.0.6

Re: [squid-users] Squid & url rewriter


Chris Robertson wrote:

John Doe wrote:

From: Merdouille 
 

#!/usr/bin/php
$temp = array();
while ( $input = fgets(STDIN) ) {
  echo "302:http://www.yahoo.fr/";;


# Flush output...
flush();

}
?>



Maybe try with a '\n'...?
  


See http://www.squid-cache.org/mail-archive/squid-users/200902/0471.html 
for a recent discussion about why this would be a bad idea.




echo and print in PHP and perl IIRC operate slightly differently.

I have found echo "blah\n"; flush(); both to be needed for PHP for 
timely results.


The earlier mail was about perl print having an implicit \n already. 
echo in PHP does not.


Amos
--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
  Current Beta Squid 3.1.0.6

Re: [squid-users] different headers for HTTP/407 answers in 2.7.STABLE6 and 3.0.STABLE9 confuses a commercial software


Dieter Bloms wrote:

Hi,

we have a commercial software, which provides the credentials to the
squid proxy, when we run the 3.0.STABLE9, but doesn't, when we run
2.7.STABLE6.

When we run 2.7.STABLE6, the client does the requests without
credentials, even when squid answers with 407 HTTP code.

the only difference I see are different header entries in the
answer from squid like Mime-Version, Proxy-Connection and Via:

3.0.STABLE9:

  HTTP/1.0 407 Proxy Authentication Required
  Server: squid
  Mime-Version: 1.0
  Date: Wed, 25 Feb 2009 15:15:20 GMT
  Content-Type: text/html
  Content-Length: 2021
  Expires: Wed, 25 Feb 2009 15:15:20 GMT
  X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
  Proxy-Authenticate: Basic realm="Proxy-Server"
  X-Cache: MISS from FQDN
  Via: 1.0 FQDN (squid)
  Proxy-Connection: close

2.7.STABLE6:

  HTTP/1.0 407 Proxy Authentication Required
  Server: squid
  Date: Wed, 25 Feb 2009 15:16:04 GMT
  Content-Type: text/html
  Content-Length: 2048
  X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
  Proxy-Authenticate: Basic realm="Proxy-Server"
  X-Cache: MISS from FQDN
  Via: 1.0 FQDN:8080 (squid)
  Connection: close

so it is possible to configure 2.7.STABLE6 that it returns the same
heades like 3.0.STABLE9 does ?

Thank you very much.


Not without removing a lot of HTTP/1.1 support.

I think you should complain to the commercial vendors. They are making 
bad assumptions about how HTTP works.


The only thing squid really has to send back is:
  HTTP/1.0 407 Proxy Authentication Required
  Date: Wed, 25 Feb 2009 15:15:20 GMT
  Proxy-Authenticate: Basic realm="Proxy-Server"


Amos
--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
  Current Beta Squid 3.1.0.6

Re: [squid-users] URL Rewrite


howard chen wrote:

Hi

Currently I am using dstdomain/cache_peer to rewrite url request from
client to backend apache (so squid act as a reverse proxy)


e.g.

acl dstdomain_site  dstdomain   .example.com


cache_peer  192.168.11.123   parent 80 0 no-query
originserver round-robin login=PASS weight=1
cache_peer_access192.168.11.123   allow dstdomain_site
cache_peer_access   192.168.11.123   deny all



This require my backend apache has a virtual host listening for .example.com

But how can I manually force rewrite an URL from user, even my
backend apache is not listening example.com?

e.g.

.example.com => .google.com

I remember this can easily done this using apache mod_rewrite
(mod_proxy) but is it possible to be done in squid?
  


See the "forceddomain" argument to cache_peer. 
http://www.squid-cache.org/Doc/config/cache_peer/



Thanks.
  


Chris

Re: [squid-users] squidaio_queue_request: WARNING - Queue congestion


Shekhar Gupta wrote:

can you please tell me how to find hit/sec .


squidclient mgr:utilization

Chris

Re: [squid-users] Problem with Reverse Proxy and multiple domains

Drew Wrobel wrote:

I made the changes you suggested, but I started getting the following error
messages in the log:

123456.com w.x.y.z - - [03/Mar/2009:12:09:45 -0500] "GET http://123456.com/ HTTP/1.1" 403 1379
"-" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; GTB5; .NET CLR 1.0.3705; .NET CLR
1.1.4322; Media Center PC 4.0)" TCP_DENIED:NONE

When I went to the web site and I get the squid ERR_ACCESS_DENIED page instead.

Here are the new lines that I had put in as you suggested. Not sure if I over
did it with the http_access lines.

Had one question thought. Since the web-server is handling both www.123456.com
and 123456.com, is the first acl valid
for both?

I also took out the entries for abcdev and 987zyx and still doesn't work. What
am I missing/doing wrong.

http_port 80 accel vhost

acl 123456 dstdomain 123456.com
acl abcdef dstdomain abcdef.com
acl 987zyx dstdomain 987zyx.com

All three of the domains should be preceded by a period. Replace these
with...

acl 123456 dstdomain .123456.com
acl abccdef dstdomain .abcdef.com
acl 987zyx dstdomain .987zyx.com

cache_peer_access 192.168.2.10 allow 123456
cache_peer_access 192.168.2.10 allow abcdef
cache_peer_access 192.168.2.10 allow 987zyx
cache_peer_access 192.168.2.10 deny all

So does the host 192.168.2.10 contain the data for all three domains?
You might want to read
http://wiki.squid-cache.org/ConfigExamples/Reverse/MultipleWebservers if
not. If it does, read and follow
http://wiki.squid-cache.org/ConfigExamples/Reverse/VirtualHosting first,
then add the redundant peers.

http_access allow 123456
http_access allow abcdef
http_access allow 987zyx

cache_peer_access 192.168.2.11 allow 123456
cache_peer_access 192.168.2.11 allow abcdef
cache_peer_access 192.168.2.11 allow 987zyx
cache_peer_access 192.168.2.11 deny all

Same question here.

http_access allow 123456
http_access allow abcdef
http_access allow 987zyx

These three lines are redundant, as http_access for these domains has
already been allowed.

cache_peer_access 192.168.2.12 allow 123456
cache_peer_access 192.168.2.12 allow abcdef
cache_peer_access 192.168.2.12 allow 987zyx
cache_peer_access 192.168.2.12 deny all
http_access allow 123456
http_access allow abcdef
http_access allow 987zyx

http_access deny all
never_direct allow all

Um. I don't think you want never_direct in a acceleration setup, unless
you are setting it up in a weird way.

Chris

Re: [squid-users] What is the reason & how to solve this


David Rodríguez Fernández wrote:

On Mon, Mar 2, 2009 at 9:11 AM, Shekhar Gupta  wrote:
  

I am running 2 squid instance on 2 Diffrent IP address on a Single server .

NIC1 - 192.168.1.1:8080 installed to /squid1/
NIC2 - 192.168.1.2:8080 installed to /squid2/

When i am specifying 192.168.1.1:8080 it takes this IP and go to
Internet whcih is Fine
When i am specifying 192.168.1.2:8080 it still takes (192.168.1.1) and
go to internet ?? what is wrong why is this happening .


You can't have two IP from the same network on different nic.
  


Sure you can.  You can also have two IPs from the same network on the 
SAME nic.  Since they are on the same network they can both directly 
access the same gateway.


Chris

Re: [squid-users] What is the reason & how to solve this


Shekhar Gupta wrote:

I am running 2 squid instance on 2 Diffrent IP address on a Single server .

NIC1 - 192.168.1.1:8080 installed to /squid1/
NIC2 - 192.168.1.2:8080 installed to /squid2/

When i am specifying 192.168.1.1:8080 it takes this IP and go to
Internet whcih is Fine
When i am specifying 192.168.1.2:8080 it still takes (192.168.1.1) and
go to internet ?? what is wrong why is this happening .
  


http://www.squid-cache.org/Doc/config/tcp_outgoing_address/

Chris

Re: [squid-users] How To Make A New Squid proxy server form the existingone...


jm...@nits.ac.in wrote:

*
This message has been scanned by IMSS NIT-Silchar

I am using the following squid version:


[r...@authdns ~]# rpm -q squid
squid-2.6.STABLE19-1.fc8
[r...@authdns ~]#

Please let me know, where this file would be located.  I tried to search,
but all efforts went invain.
  


rpm -ql squid | grep QUICKSTART

Chris

Re: [squid-users] Squid & url rewriter


John Doe wrote:

From: Merdouille 
  

#!/usr/bin/php
$temp = array();
while ( $input = fgets(STDIN) ) {
  echo "302:http://www.yahoo.fr/";;


# Flush output...
flush();

}
?>



Maybe try with a '\n'...?
  


See http://www.squid-cache.org/mail-archive/squid-users/200902/0471.html 
for a recent discussion about why this would be a bad idea.



JD

  


Chris

RE: [squid-users] Problem with Reverse Proxy and multiple domains

2009-03-03 Thread Drew Wrobel


I made the changes you suggested, but I started getting the following error 
messages in the log:

123456.com w.x.y.z - - [03/Mar/2009:12:09:45 -0500] "GET http://123456.com/ 
HTTP/1.1" 403 1379 "-" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; 
GTB5; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 4.0)" 
TCP_DENIED:NONE

When I went to the web site and I get the squid ERR_ACCESS_DENIED page instead.

Here are the new lines that I had put in as you suggested.  Not sure if I over 
did it with the http_access lines.

Had one question thought.  Since the web-server is handling both www.123456.com 
and 123456.com, is the first acl valid
for both?

I also took out the entries for abcdev and 987zyx and still doesn't work.  What 
am I missing/doing wrong.


http_port 80 accel vhost

acl 123456 dstdomain 123456.com
acl abcdef dstdomain abcdef.com
acl 987zyx dstdomain 987zyx.com


cache_peer_access 192.168.2.10 allow 123456
cache_peer_access 192.168.2.10 allow abcdef
cache_peer_access 192.168.2.10 allow 987zyx
cache_peer_access 192.168.2.10 deny all
http_access allow 123456
http_access allow abcdef
http_access allow 987zyx


cache_peer_access 192.168.2.11 allow 123456
cache_peer_access 192.168.2.11 allow abcdef
cache_peer_access 192.168.2.11 allow 987zyx
cache_peer_access 192.168.2.11 deny all
http_access allow 123456
http_access allow abcdef
http_access allow 987zyx


cache_peer_access 192.168.2.12 allow 123456
cache_peer_access 192.168.2.12 allow abcdef
cache_peer_access 192.168.2.12 allow 987zyx
cache_peer_access 192.168.2.12 deny all
http_access allow 123456
http_access allow abcdef
http_access allow 987zyx

http_access deny all
never_direct allow all


> Date: Tue, 3 Mar 2009 11:10:08 +1300
> Subject: Re: [squid-users] Problem with Reverse Proxy and multiple domains
> From: squ...@treenet.co.nz
> To: phoenix1...@hotmail.com
> CC: squid-users@squid-cache.org
> 
>>
>> I'm currently running Squid 2.6 stable 22 as a caching server.
>>
>> It is acting as a front-end for bunch of servers answering for
>> www.123456.com and 123456.com.  Without any problems.
>>
>> I have updated the apache configuring for handling web traffic for
>> www.abcdef.com=2C abcdef.com=2C www.987zyx.com and 987zyx.com.
>>
>> If I hit the web servers with the various domains=2C I get the desired web
>> site without any problems.
>>
>> The problem I'm running into with Squid is that no matter what domain I
>> enter,  squid is treating all the traffic for www.123456.com.
>>
>> So if I enter www.987zyx.com via squid=2C I go the www.123456.com web site
>> instead.
>>
>> Here is a copy of the squid configuration I'm using.  What am I doing
>> wrong?
>>
> 
> Using the broken and obsolete squid-2.5 method of 'acceleration'.
> 
> I've placed incline alterations to update this to 2.6 requirements...
> 
>>
>> acl all src 0.0.0.0/0.0.0.0
>> acl manager proto cache_object
>> acl localhost src 127.0.0.1/255.255.255.255
>> acl to_localhost dst 127.0.0.0/8
>> acl SSL_ports port 443
>> acl CONNECT method CONNECT
>>
>> hierarchy_stoplist cgi-bin ?
>> acl QUERY urlpath_regex cgi-bin \?
>> cache deny QUERY
>> acl apache rep_header Server ^Apache
>> broken_vary_encoding allow apache
>> coredump_dir /var/cache/squid
> 
>> http_port 80 accel vport
> 
> http_port 80 accel vhost
> 
>> cache_peer 192.168.2.10 parent 80 0 no-query originserver round-robin
>> login=PASS
>> cache_peer 192.168.2.11 parent 80 0 no-query originserver round-robin
>> login=PASS
>> cache_peer 192.168.2.12 parent 80 0 no-query originserver round-robin
>> login=PASS
> 
> KILL this:
>> acl webserver dst 192.168.2.10 192.168.2.11 192.168.2.12
> 
> acl 123456 dstdomain .123456.com
> 
> (if you want to be VERY tricky:
>acl 123456 dst 192.168.2.10
> )
> 
> cache_peer_access 192.168.2.10 allow 123456
> cache_peer_access 192.168.2.10 deny all
> http_access allow 123456
> 
> ... repeat as appropriate for each webserver. Including _separate_ ACLs
> for each one.
> 
> Followed with:
>  http_access deny all
>  never_direct allow all
> 
> Kill all the below http_*:
> 
>> http_access allow webserver
>> http_access allow all
>> miss_access allow webserver
>> miss_access allow all
>> http_access deny all
>>
> 
>> icp_access deny all
>>
>> acl loadbalancer1 src 192.168.3.125
>> acl loadbalancer2 src 192.168.3.126
>> follow_x_forwarded_for allow loadbalancer1
>> follow_x_forwarded_for allow loadbalancer2
>> follow_x_forwarded_for allow all
>> acl_uses_indirect_client on
>> delay_pool_uses_indirect_client on
>> log_uses_indirect_client on
>>
>> logformat combined %{Host}>h %>a %ui %un [%tl] "%rm %ru HTTP/%rv" %Hs %h"
>> "%{User-Agent}>h" %Ss:%Sh
>> access_log /var/log/squid/access.log combined
>> collapsed_forwarding on
>> vary_ignore_expire on
>>
>> cache_effective_user squid
>> cache_store_log none
>> client_db off
>> cache_mem  512 MB
>> cache_dir ufs /var/cache/squid 3000 10 10
>>
> 
> Amos
> 
> 

_
Hotmail® is up to 70% faster.

[squid-users] squid and ftp

2009-03-03 Thread shailesh shinde

why does squid not support ftp ,smtp like protocols on the client side.
Is it possible to write modules for such a support ?

If yes what would be the feasibility of the work because we are a
group of 3 third year computer engineering students willing to do our
final year project on squid.

Please guide us.

--
regards
Shailesh

Re: [squid-users] Logging with emulate_httpd_log in reverse proxy with rewriter and 2.7

2009-03-03 Thread Simon Waters

On Saturday 28 February 2009 11:28:54 Amos Jeffries wrote:
> Simon Waters wrote:
> > Upgraded from 2.6 to 2.7 (Debian Etch to Debian Lenny).
... SNIP ...
> > Is this a deliberate change between 2.6 and 2.7?
... SNIP ...
>
> I think this was a bug fixed in 2.7.STABLE4, which has not quite yet
> made its way into Debian. Please log a bug with Debian against that.

Thanks Amos,

I snaffled the 2.7stable6-1 from the Debian Squeeze and Sid repositories 
(Packages: squid, squid-common and libdb4.7), and can confirm that this fixes 
the observed problem  (logging request from squid, not request to squid).

[squid-users] URL Rewrite

2009-03-03 Thread howard chen

Hi

Currently I am using dstdomain/cache_peer to rewrite url request from
client to backend apache (so squid act as a reverse proxy)


e.g.

acl dstdomain_site  dstdomain   .example.com


cache_peer  192.168.11.123   parent 80 0 no-query
originserver round-robin login=PASS weight=1
cache_peer_access192.168.11.123   allow dstdomain_site
cache_peer_access   192.168.11.123   deny all



This require my backend apache has a virtual host listening for .example.com

But how can I manually force rewrite an URL from user, even my
backend apache is not listening example.com?

e.g.

.example.com => .google.com

I remember this can easily done this using apache mod_rewrite
(mod_proxy) but is it possible to be done in squid?

Thanks.

Re: [squid-users] Squid and NTLM Authentication

2009-03-03 Thread Ryan McCain

>>> On Mon, Mar 2, 2009 at  5:36 PM, in message
, "Amos
Jeffries"  wrote: 
>>  We are using squid-2.5.STABLE12-18.12
>>
> 
> Please use a newer more capable Squid.  There have been MANY improvements
> since 2.5 was made obsolete.
> 
> Amos

The only reason we are using  that version is because it's the latest version 
supported w/ SLES 10.   Does this version or a newer version support the 
scenario I described?

Thanks..

Re: [squid-users] squidaio_queue_request: WARNING - Queue congestion

2009-03-03 Thread Shekhar Gupta

can you please tell me how to find hit/sec .

On Tue, Mar 3, 2009 at 7:00 PM, Kinkie  wrote:
> On Tue, Mar 3, 2009 at 11:03 AM, Shekhar Gupta  
> wrote:
>> I am getting this log in cache.log file . I am running with 280GB
>> cach_dir with aufs ... Can any one suggest what can be done to resolve
>> this .
>
> Is your cache overloaded?
> 280 Gb is a LOT.. how many hits/second are you getting?
>
>
> --
>    /kinkie
>

Re: [squid-users] squidaio_queue_request: WARNING - Queue congestion

2009-03-03 Thread Kinkie

On Tue, Mar 3, 2009 at 11:03 AM, Shekhar Gupta  wrote:
> I am getting this log in cache.log file . I am running with 280GB
> cach_dir with aufs ... Can any one suggest what can be done to resolve
> this .

Is your cache overloaded?
280 Gb is a LOT.. how many hits/second are you getting?


-- 
/kinkie

Re: [squid-users] Problems enabling cache_replacement_policy

2009-03-03 Thread Manuel Trujillo

On Tue, Mar 3, 2009 at 09:50, Amos Jeffries  wrote:
> memory_replacement_policy heap GDSF
> high_memory_warning 2048 MB

> ... oops. no more cache_dir to use heap with. Stop.

Thank you Amos. I don't know anything about the order with certains commands.

Solved ;-)

-- 
Manuel Trujillo

Re: [squid-users] delaypolls

so the correct syntax is :

delay_pools 2
delay_class 1 1
delay_parameters 1 32000/64000
delay_access 1 allow domain-nakal !free
delay_access 1 allow nakal  !free
delay_access 1 deny ALL

delay_class 2 1
delay_parameters 2 1000/1000 1000/2800
delay_access 2 allow porn !free
delay_access 2 deny ALL



about class 2 is correct ?

On Fri, Feb 27, 2009 at 3:53 PM, Amos Jeffries  wrote:
> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> can you fix it for me ?
>>
>> i want user access class 1 got 32000 but they can burst to 64000
>>
>
> Just change the "a/b" parts as you need.
> The numbers are /  and count bytes.
>
> Amos
> - Show quoted text -
>
>> and when class 2 same thing but with lower b/w
>>
>> On Fri, Feb 27, 2009 at 3:36 PM, Amos Jeffries 
>> wrote:
>>>
>>> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

 delay_parameters 1 32000/32000 2500/64000
>>>
>>> (class 1) All people assigned into this pool share a single 32000 byte
>>> per
>>> second pipe.
>>>
>>> The other parameters 250/64000 is garbage, since a class 1 pool only has
>>> one
>>> set of speed parameters.
>>>
 and
 delay_parameters 2 1000/1000 1000/2800
>>>
>>> (class 2) people assigned into this pool all share a 1000 byte per second
>>> pipe.
>>> Individual people start off with 2800 (or maybe only 1000) bytes, but are
>>> limited to 1000 per second once they start downloading.
>>>
>>> I'm not sure what Squid does when one IP is allowed a higher starting
>>> bytes
>>> than the entire group, its probably not good.
>>>
 On Fri, Feb 27, 2009 at 2:36 PM, Amos Jeffries 
 wrote:
>
> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> what is this paramenter mean ?
>>
>> acl domain-nakal url_regex -i "/etc/squid/domain-nakal.txt"
>> acl nakal url_regex -i "/etc/squid/ext-nakal.txt"
>> acl porn url_regex -i "/etc/squid/porn.txt"
>>
>> delay_pools 2
>> delay_class 1 1
>> delay_parameters 1 32000/32000 2500/64000
>> delay_access 1 allow domain-nakal !free
>> delay_access 1 allow nakal  !free
>> delay_access 1 deny ALL
>>
>> delay_class 2 1
>> delay_parameters 2 1000/1000 1000/2800
>> delay_access 2 allow porn !free
>> delay_access 2 deny ALL
>>
>>
>> please tell me in english
>>
> Which one? you list many,many parameters.
>
>
> Amos
> --
> Please be using
>  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>  Current Beta Squid 3.1.0.5
>


>>>
>>> --
>>> Please be using
>>>  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>>>  Current Beta Squid 3.1.0.5
>>>
>>
>>
>>
>
>
> --
> Please be using
>  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>  Current Beta Squid 3.1.0.5
>



-- 
-=-=-=-=
Personal Blog http://my.blog.or.id ( lagi belajar )
Hot News !!! : Pengin punya Layanan SMS PREMIUM ? Contact me ASAP.
dapatkan Share revenue MAXIMAL tanpa syarat traffic...

Re: [squid-users] delaypolls

so the correct syntax is :

delay_pools 2
delay_class 1 1
delay_parameters 1 32000/64000
delay_access 1 allow domain-nakal !free
delay_access 1 allow nakal  !free
delay_access 1 deny ALL

delay_class 2 1
delay_parameters 2 1000/1000 1000/2800
delay_access 2 allow porn !free
delay_access 2 deny ALL



about class 2 is correct ?

On Fri, Feb 27, 2009 at 3:53 PM, Amos Jeffries  wrote:
> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> can you fix it for me ?
>>
>> i want user access class 1 got 32000 but they can burst to 64000
>>
>
> Just change the "a/b" parts as you need.
> The numbers are /  and count bytes.
>
> Amos
> - Show quoted text -
>
>> and when class 2 same thing but with lower b/w
>>
>> On Fri, Feb 27, 2009 at 3:36 PM, Amos Jeffries 
>> wrote:
>>>
>>> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

 delay_parameters 1 32000/32000 2500/64000
>>>
>>> (class 1) All people assigned into this pool share a single 32000 byte
>>> per
>>> second pipe.
>>>
>>> The other parameters 250/64000 is garbage, since a class 1 pool only has
>>> one
>>> set of speed parameters.
>>>
 and
 delay_parameters 2 1000/1000 1000/2800
>>>
>>> (class 2) people assigned into this pool all share a 1000 byte per second
>>> pipe.
>>> Individual people start off with 2800 (or maybe only 1000) bytes, but are
>>> limited to 1000 per second once they start downloading.
>>>
>>> I'm not sure what Squid does when one IP is allowed a higher starting
>>> bytes
>>> than the entire group, its probably not good.
>>>
 On Fri, Feb 27, 2009 at 2:36 PM, Amos Jeffries 
 wrote:
>
> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> what is this paramenter mean ?
>>
>> acl domain-nakal url_regex -i "/etc/squid/domain-nakal.txt"
>> acl nakal url_regex -i "/etc/squid/ext-nakal.txt"
>> acl porn url_regex -i "/etc/squid/porn.txt"
>>
>> delay_pools 2
>> delay_class 1 1
>> delay_parameters 1 32000/32000 2500/64000
>> delay_access 1 allow domain-nakal !free
>> delay_access 1 allow nakal  !free
>> delay_access 1 deny ALL
>>
>> delay_class 2 1
>> delay_parameters 2 1000/1000 1000/2800
>> delay_access 2 allow porn !free
>> delay_access 2 deny ALL
>>
>>
>> please tell me in english
>>
> Which one? you list many,many parameters.
>
>
> Amos
> --
> Please be using
>  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>  Current Beta Squid 3.1.0.5
>


>>>
>>> --
>>> Please be using
>>>  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>>>  Current Beta Squid 3.1.0.5
>>>
>>
>>
>>
>
>
> --
> Please be using
>  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
>  Current Beta Squid 3.1.0.5
>



-- 
-=-=-=-=
Personal Blog http://my.blog.or.id ( lagi belajar )
Hot News !!! : Pengin punya Layanan SMS PREMIUM ? Contact me ASAP.
dapatkan Share revenue MAXIMAL tanpa syarat traffic...

[squid-users] squidaio_queue_request: WARNING - Queue congestion

2009-03-03 Thread Shekhar Gupta

I am getting this log in cache.log file . I am running with 280GB
cach_dir with aufs ... Can any one suggest what can be done to resolve
this .

Re: [squid-users] Squid 3.1 Release Date

2009-03-03 Thread Silamael

Amos Jeffries wrote:
> We don't exactly date things here. With everyone working on voluntary
> time its unpredictable. Though there has been a fairly regular 4-week
> cycle for new X.Y.0.z beta releases.
> 
> For planning and upgrade testing, 3.1.0.6 is a fairly stable point to
> begins with.
> 
> Back before we/I decided to adopt the fluid feature inclusion we had a
> set of approved features for 3.1. The last of these given a guarantee of
> being in 3.1 is still grinding it's way through testing (far too
> slowly). I expect that will take us through March and maybe April before
> 3.1 gets a chance of even starting the stable waiting period.
> 
> There is also a short list of RC bugs which we consider major enough to
> need fixing before we call it stable.
> Many of these bugs are only confirmed to exist in 3.0. But they are
> serious enough that we really NEED someone who can see them in 3.0 to
> test 3.1 and confirm they are not still hiding.
> 
> Last time I had to guesstimate a timeline I said mid-year (june/july)
> 2009, I've seen no reason to change it for better or worse yet.
> 
> Amos

Thank you for your answer Amos. This is exactly what i wanted to know.

-- Matthias

Re: [squid-users] Problems enabling cache_replacement_policy


Manuel Trujillo wrote:

On Tue, Mar 3, 2009 at 00:33, Amos Jeffries  wrote:

Many things in squid.conf are order-specific.


Humm... I don't know this...


The cache_replacement_policy setting can be used multiple times, and only
affects the cache_dire defined below it.


This is the part about this in my config file:


## PARAMETROS CACHE



squid in memory has default LFU scheme


#cache_dir aufs /var/cache/squid 81920 16 64
cache_dir aufs /var/cache/squid 40960 16 64


... creates cache_dir with all settings (including LFU) ...


pid_filename /var/run/squid.pid


## TUNING EN CASO NECESARIO (a descomentar)

#client_db off


## PARAMETRIZACION DE LA CACHE MEMORIA

cache_replacement_policy heap GDSF


.. changes default policy to heap GDSF ...



memory_replacement_policy heap GDSF
high_memory_warning 2048 MB


... oops. no more cache_dir to use heap with. Stop.



Is this right?


no. see above.

Amos
--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
  Current Beta Squid 3.1.0.5

Re: [squid-users] Squid 3.1 Release Date