On 25/04/18 01:41, Tobias Wolter wrote:
> Cheers,
>
> On Mon, 2018-04-23 at 22:54 +0200, Tobias Wolter wrote:
>> Kudos for the hints, Amos, they're great and'll help me a lot
>> (tomorrow, it's 22.54 local here).
>
> Welp, we haven't really come that far, but what we can tell is that
> Squid isn'
Wow, a lot to read (and understand, for a newbie like me :-|)
From what i've seen it's sufficient to insert the "workers n" directive in
the conf (n number of workers). With some limitations with the features that
support SMP (delay pools, cache, etc - i not think to use any of them)
--
Sent
On 04/24/2018 06:14 AM, masterx81 wrote:
> I've configured squid with ssl_bump and now the squid process (not the
> helpers) takes quite load. There aren't too much clients on it (max 50).
> I've already increased the number of vcpu for the machine, but the only
> process that i see eating cpu is
Cheers,
On Mon, 2018-04-23 at 22:54 +0200, Tobias Wolter wrote:
> Kudos for the hints, Amos, they're great and'll help me a lot
> (tomorrow, it's 22.54 local here).
Welp, we haven't really come that far, but what we can tell is that
Squid isn't at fault by itself, as we merely forced it to cache
Hi!
I've configured squid with ssl_bump and now the squid process (not the
helpers) takes quite load. There aren't too much clients on it (max 50).
This is the config (ripped some acl to make it readable):
--
cache_mgr x...@xxx.com
visible_hostn
On 24/04/18 10:46, Vishali Somaskanthan wrote:
> Hi all,
>
> I am working on opening up a persistent connection from Squid -> server.
> i have 2 questions.
>
> 1. I find Squid sometimes sends a [FIN, ACK] signal to server as a
> result of which, Squid sends RST and resets the connection. Ideally
I've tried to comment out the "tcp_outgoing_address 0.0.0.0 all" directive as
you suggested, and actually all work as it should. Not know why in the past
had to add it.
By now, only one site has problem with ssl_bump and ipv6, and it's
wiki.squid-cache.org (quite hilarious). If i bump it i get the
