On 9/14/21 3:04 PM, Moti Berger wrote:
> I have the followings in squid.conf:
>
> logformat metrics %icap::tt %adapt::all_trs %adapt::sum_trs
> %{service_req_a}adapt::sum_trs %{service_resp_a}adapt::sum_trs
> %{service_req_b}adapt::sum_trs %{service_resp_b}adapt::sum_trs
>
On 15/09/21 10:28 pm, L.P.H. van Belle wrote:
Hai Amos,
Thanks on the reply, ive missed the change from db to tdb, thanks on that.
What i notice in the builds is,
I see this one..
config.status: creating test-suite/Makefile
And then i see these, then it failes.
cp ../../src/tes
Hai Amos,
Thanks on the reply, ive missed the change from db to tdb, thanks on that.
What i notice in the builds is,
I see this one..
config.status: creating test-suite/Makefile
And then i see these, then it failes.
cp ../../src/tests/stub_fd.cc tests/stub_fd.cc
cp: cannot create
Hey Amos and Alex,
I have tested the 4.16 version and it seems to work steady on basic loads.
Eliezer
-Original Message-
From: squid-announce On
Behalf Of Amos Jeffries
Sent: Thursday, July 22, 2021 7:24 AM
To: squid-annou...@lists.squid-cache.org
Subject: [squid-announce] Squid 4.16
Many thanks
It fix the issue !
Le 15/09/2021 à 13:08, Graham Wharton a écrit :
You see this when starting as non rootuser. Squid should be started as
root and then it changes identity to cache effective user as defined
in config when it forks.
Graham Wharton
Lube Finder
Tel (UK) : 0800 955
How do you build and start it, init.d/squid or systemd start squid
In case of last, what i suspect, I seen more if these messages on previous
version..
But all my version dont show this on Debian 10.
This is my latest startup for systemd
# /lib/systemd/system/squid.service
## Copyright (C)
On Debian 10 64bits with squid 5.1 we have thousand warning as this:
2021/09/15 08:00:18 kid1| WARNING: no_suid: setuid(0): (1) Operation not
permitted
2021/09/15 08:00:18 kid2| WARNING: no_suid: setuid(0): (1) Operation not
permitted
2021/09/15 08:00:18 kid1| WARNING: no_suid: setuid(0): (1)
On 15/09/21 1:21 pm, Grant Taylor wrote:
On 9/14/21 6:09 PM, Amos Jeffries wrote:
b) If those upstream servers are embedding URLs for clients to
directly contact the XaaS services. Then your desire is not possible
without redesigning the upstream service(s) such that they stop
exposing their
