Hello,
I thought I would make everyone on this list aware of an issue between squid 3.4.x (and perhaps 3.5?) and FreeBSD 10.1-RELEASE. There was a regression in the FreeBSD 10.1-RELEASE kernel's signal handling behavior that causes squid to coredump and restart itself when receiving the shutdown signal (i.e., squid -k shutdown). The problem has been fixed in FreeBSD 10.1-STABLE (10/stable), but will likely not be applied to 10.1-RELEASE (releng/10.1). So it is bound to affect many squid users running FreeBSD.
More information about the kernel bug can be found here:
There is an ongoing discussion about how it affects the squid port here:
The working fix is to apply two different patches to the 10.1-RELEASE kernel and run off a custom kernel. Perhaps there is some kind of workaround squid could employ if the problem is not fixed in 10.1-RELEASE? I'm not suggesting this as a good idea, and I'm personally comfortable with running a custom kernel as I do this already, but it seems that a lot of people are starting to run into this problem who are not so comfortable.
Hopefully this helps someone running into this strange problem.
-Nick
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
