On 14/02/2013 1:07 p.m., David Touzeau wrote:
-----Original Message----- From: Amos Jeffries
Sent: Wednesday, February 13, 2013 2:17 AM
To: squid-users@xxxxxxxxxxxxxxx
Subject: Re: Squid 3.3x: UNLNK id(232) Error: no
filename in shm buffer
On 13/02/2013 1:29 a.m., David Touzeau wrote:
Dear
I have these errors on Squid 3.3
What does it means ?
We recently added a number of messages similar to this one to report
error codes coming out of the kernel which were previously ignored for
no documented reason. This one appears to be happening a lot due to a
massive amount of empty IPC packets flowing around. We are still trying
to figure that out exactly what that means to decide the best way to
silence or fix it.
There is a workaround patch which can be used to quiet Squid meanwhile
in http://bugs.squid-cache.org/show_bug.cgi?id=3763.
PS. if you have any interest in a proper fix, or insight that helps
please comment on the bug report.
Amos
Hi Amos,
I have a robot that compile every "nightly/daily" builds from packages
posted to squid-cache.org.
Is these kind of fixes are included in these builds...?
If it is an experiment patch in bugzilla, no. If it has been confirmed
as working and applied to Squid, yes. I post to the bug reports as a
back-port the fix to each version.
For the record, we now found the working fix and it is in 3.HEAD, and
about to go to 3.3 and 3.2 in the next few hours for tomorrows snapshot.
Amos