Version 1.1.20

Hi,

        We are experiencing problems with this version of squid. What it
does is it starts taking up all the machines CPU, and in effect starving
other processes. The squid process goes into a WAIT state.

        We are running Digital Unix V4.0 OSF/1 on an Alpha 255/300mHz

        It's last "episode" of this has lasted for about 3/4 of an hour,
and still going .... what's happening?? Here is a more detailed list of
our configuration:

We have 3 instance of these machines, all siblings:

Machine: DEC Alpha 255/300mHz
O/S: Digital Unix V4.0 OSF/1
RAM: 512 Mb
Disk: 10gig ( 2*4gig external, 1*2gig internal )
Network: 100 Mbps
Disk config: 1 * 4 gig -> squid cache
                1 * 4 gig -> binaries (inc. squid)
                1 * 2 gig -> system disk
Squid: cache_mem 120 (allowing * 3 normal growth for hot objs)
                cache_swap 3500 ( 500 meg buffer to max disk )
                swap_level1_dirs 32
                swap_level2_dirs 128

We have three of these in sibling relationships. All three are doing
authentication. I have written a work around into the code that fixes the
sibling authentication problem in squid's native authentication mode.

I have re-written the proxyAuthentication code so it actually does remote
authentication, and caches the information. I have tested this code and
it is not the problem.

Any assistance is very much appreciated.

Thanks,

Dave.

-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
David Richards Ph: +61 7 3864 4347
Network Programmer Fax: +61 7 3864 5272
Computing Services E-mail: dj.richards@qut.edu.au
Queensland University of Technology
Brisbane, Australia
-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
Received on Tue Jan 27 1998 - 18:31:18 MST