Hey Antony and Ben,
I have verified that the Pinger process is at fault.
I don't know if it's a bug or not.
You can disable pinger and it will work:
http://www.squid-cache.org/Doc/config/pinger_enable/
pinger_enable off
will resolve this issue.
All The Bests,
Eliezer
Eliezer Croitoru
Hi people, years ago I was a squid user, time has passed and I need to
implement again on the personal laptop (which my 9-year-old daughter uses),
that she cannot access to search for certain words.
Install squid for windows 10, I generated the following acl to detect words
that can be searched
On 3/13/22 19:49, Dave Blanchard wrote:
On Sun, 13 Mar 2022 18:38:05 -0400 Alex Rousskov wrote:
kill -9 will not kill SMP Squid workers and other kid
processes. To a large degree, Squid will just keep running as if nothing
happened -- that signal cannot be caught and processed specially by the
On Monday 14 March 2022 at 05:42:35, ben wrote:
> Hi Eliezer,
>
> SQUID started listening only after I run "ip6tables -P INPUT ACCEPT".
Without seeing the rest of your iptables rules, it's not clear whether this
really does apply to every interface and every protocol, or whether there are
> "kill -9" will definitely leave some things in an odd state. Try the
> double-kill first.
On Sun, 13 Mar 2022 18:38:05 -0400
Alex Rousskov wrote:
Just to add: kill -9 will not kill SMP Squid workers and other kid
processes. To a large degree, Squid will just keep running as if nothing
Hey Ben,
As I suspected it's the pinger that is causing this issue.
In my RPM builds it's disabled by defaults to avoid selinux complications.
I think it's a very special case you have found.
Try to use the:
pinger_enable off
and see if it fixes your issue.
All The Bests,
Eliezer
Eliezer
Hey Ben,
I do not know if it won't listen.
I can try to reproduce locally and see the results.
I assume it might be related to the pinger process or maybe something else but
not 100% sure.
Eliezer
Eliezer Croitoru
NgTech, Tech Support
Mobile: +972-5-28704261
Email: ngtech1...@gmail.com
