-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've confirmed that the attached patch fixes this bug and renders squid
reliable on my system. See notes in previous postings.
Steve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Changing the above code (with the fprintf's) from 0.99L to 0.99f makes
squid reliable on my system.
I can't claim to understand this code, but it seems that was a typo.
0.99L translates to integer "1" on gcc-3.3.5-3. It looks like the
intention
I rebuilt the code from the Debian source archive (version 2.5.9-9), and
changed StatHist.c line 93 to this:
{
double shv = statHistVal(H, 0);
double answer = floor(0.99L + shv - min);
int iAnswer = (int) answer;
if (iAnswer != 0) { // ### Stephen Blackheath
fprintf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luigi,
Much much appreciated. See requested information below.
It ran for around 5 hours this time. Also see below the changes I've
made to the Squid config file. My setup is like this: I am running
Dansguardian as a transparent proxy (using some
Package: squid
Version: 2.5.9-9
Severity: important
Squid runs for hours to a couple of days, then - without any client
requests - stops running, with the assertion failure below. These
references suggest it might be a compile problem:
http://www.squid-cache.org/mail-archive/squid-users/25/02
5 matches
Mail list logo
