On 12/10/18 12:34 PM, L A Walsh wrote:
> I seem to have a problem specifying the cipher list in the tls_outgoing
> options.
> The line I have:
> tls_outgoing_options
> options=NOSSLv3,SINGLE_DH_USE,SINGLE_ECDH_USE,cipher=EECDH+ECDSA+AESGCM:\
Comma .^
>
I seem to have a problem specifying the cipher list in the tls_outgoing
options.
The line I have:
tls_outgoing_options
options=NOSSLv3,SINGLE_DH_USE,SINGLE_ECDH_USE,cipher=EECDH+ECDSA+AESGCM:\
EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:\
On 10/11/2018 06:30 AM, Joseph Jones wrote:
> I'm trying to find a root cause for failed workers.
My suggestions:
0. Upgrade to the latest Squid v4.
1. Disable memory cache:
cache_mem 0
2. Maintain one cache.log per worker. For example:
cache_log
On 10/11/2018 02:15 AM, juju wrote:
> on http://www.squid-cache.org/Doc/config/cache_dir/:
> "In SMP configurations, cache_dir must not precede the workers option
> and should use configuration macros or conditionals to give each worker
> interested in disk caching a dedicated cache directory"
>
I'm trying to find a root cause for failed workers. We have three squid
instances that act as transparent forward proxies that limit internet
connectivity for our network by doing url whitelisting. Current throughput per
instances is about 90MB/s. after a restart of squid all workers seem to
Hello !
Thank you very much Alex and AmosI have 2 real cores so it will be good.
on http://www.squid-cache.org/Doc/config/cache_dir/ (available in: 4 3.5
3.4 3.3 3.2 2.7 3.1 3.0 2.6) :"In SMP configurations, cache_dir
must not precede the workers option and should use
Greeting all,
The online repository with latest Squid 4.3 (rebuilt from Debian unstable with
sslbump support) for Ubuntu 18 LTS 64-bit is available at squid43.diladele.com.
Github repo at https://github.com/diladele/squid-ubuntu contains the scripts we
used to make this compilation.
Hope you
