Amos,
Systemd can be define to run a specific command for a "reload" and even if
nobody wrote the line in a service file it's there since almost day one of
systemd services.
And.. if the version is el6 I believe it's still a sysVinit based system.
Squid -kparse should detect and squid -kreconf
On 07/06/18 11:11, Cheadle, Edward wrote:
> Squid version 3.5.27-1.el6
>
...
>
> The FATAL error messages below is because I added a line with dstdomain
> in it when there were already an entry with dstdom_regex in it.
>
> I assume that is the “type” that is talked about.
>
Correct.
>
> 2018
Eliezer,
It now seems from working on the squid issue that the problem is not in squid.
All of your suggestions were helpful when I started working through the issues.
We now think that something in the Code used to build the ASG caused whatever
timeout we were seeing.
I am now trying to get to
Squid version 3.5.27-1.el6
Linux: Amazon Linux AMI 2018.03.0
I saw the warning messages below in squid.out, did some research and found out
that the messagesseemed to be caused the two lines:
acl localhost src 127.0.0.1/32
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32
From http://www.squid-cache.
>If you are using SSL-Bump features, please consider Squid-4 instead
It is not used at all.Squid does not work with ssl. Frontend only
Concerning incorrectly specified options at build
Here on this squid happens the same thing:
* squid3 -v*
*Squid Cache: Version 3.4.8*
* linux*
*configure opti
OK so I took some time to understand and hack amazon linux 1 and. based on
the docker container I created a kvm guest VM build node.
I could have used the docker container but I like a static VM much more.
The result packages are at:
http://ngtech.co.il/repo/amzn/
which have packages for
