> > Just wait the next 3.5.x release.
> >
>
> Or todays 3.5 snapshot r13752 has the fixes in it.
>
> Amos
> ___
Great, I am going to be able to justify my time to my manager :)
And step away from the aspirin bottle ...
Regards,
Fred
http://
On 10/02/2015 10:19 p.m., FredB wrote:
>
>> About Squid 3.5 wait for the moment, the 100 % CPU bug is present and
>> I will make deep tests to be sure that there is nothing else.
>> When this bug will be fixed and my tests (with High load) are all ok
>> I will post a message here, don't worry abou
> About Squid 3.5 wait for the moment, the 100 % CPU bug is present and
> I will make deep tests to be sure that there is nothing else.
> When this bug will be fixed and my tests (with High load) are all ok
> I will post a message here, don't worry about that.
Ok, we have worked with Amos and th
>
>
> Hello,
>
> Fred what should I do exactly ? Sorry I'm a little bit lost
>
> Thanks
>
Hmm, You can still use your 3.4.x version + my patch, but I think it should be
better to use the latest 3.4 snapshot there are some interesting bug-fixes and
the patch was pushed by Amos yesterday.
>
>
>
> Hello all,
>
> Unfortunately the problem still present with latest snapshot, there is a ldap
> request for each GET or CONNECT and with heavy load this is really
> problematic.
> You can take a look at my bug rapport, there is a temporary solution for 3.5,
> but I guess it's better
> Aye sorry I got my mail threads a bit mixed up there.
>
> Digest is helped, but nowhere near fixed by that bug 3997 fix.
>
>
> PS. FredB can you try to catch me in a day or two on IRC again to go
> over your Digest patches? I decided to go with them, but had
> something
> to query first (cant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/01/2015 3:55 a.m., FredB wrote:
>
>
> , but I guess it's better to stay with 3.4 with my patch (if
>> you suffer from bug 4066 of course) for the moment.
>>
>>
>
> I'm speaking only about DIGEST identification, of course
>
Aye sorry I
, but I guess it's better to stay with 3.4 with my patch (if
> you suffer from bug 4066 of course) for the moment.
>
>
I'm speaking only about DIGEST identification, of course
___
squid-users mailing list
squid-users@lists.squid-cache.org
http:/
> >
> > I'm trying to test Squid 3.5.1 configured with digest
> > authentication, and with high load Squid eats 100% CPU I had no
> > problem with 3.4 and the patch from your previous message (
> > http://www.mail-archive.com/squid-users@lists.squid-cache.org/msg00925.html
> > )
> >
> > The prob
An: squid-users@lists.squid-cache.org
> Betreff: Re: [squid-users] Squid 3.5.1 100% CPU
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 19/01/2015 10:36 p.m., wmunny william wrote:
> > Hello,
> >
> > I'm trying to test Squid 3.5.1 configured with dige
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/01/2015 10:36 p.m., wmunny william wrote:
> Hello,
>
> I'm trying to test Squid 3.5.1 configured with digest
> authentication, and with high load Squid eats 100% CPU I had no
> problem with 3.4 and the patch from your previous message (
> http:/
Hello,
I'm trying to test Squid 3.5.1 configured with digest authentication, and with
high load Squid eats 100% CPU
I had no problem with 3.4 and the patch from your previous message (
http://www.mail-archive.com/squid-users@lists.squid-cache.org/msg00925.html )
The problem is gone with BASIC
12 matches
Mail list logo
