create it, and wokrer just attaches to it.
Alex
> Subject: Re: [squid-users] cannot leave empty workers
> To: alex_wu2...@hotmail.com; squid-users@lists.squid-cache.org
> From: squ...@treenet.co.nz
> Date: Sat, 25 Jul 2015 12:54:47 +1200
>
> On 25/07/2015 11:53 a.m., Alex Wu
On 25/07/2015 11:53 a.m., Alex Wu wrote:
> further analysis indicated that master process created
> quid-ssl_session_cache.shm.
>
> In other words, it needs a https_port or http_port with ssl-bump in outside
> any process number to create this shared memeory segment.
>
> Furthermore, the code
...@treenet.co.nz; squid-users@lists.squid-cache.org
Date: Fri, 24 Jul 2015 15:28:06 -0700
Subject: Re: [squid-users] cannot leave empty workers
There is a problem
The code isSslServer looks for https configuration. If no one found, it will
not create /run/shm/ssl_session_cache.shm.
Late, the code
.
THX
Alex
> To: squid-users@lists.squid-cache.org
> From: squ...@treenet.co.nz
> Date: Sat, 25 Jul 2015 10:07:18 +1200
> Subject: Re: [squid-users] cannot leave empty workers
>
> On 25/07/2015 7:24 a.m., Alex Wu wrote:
> > If I define 4 workers, and use the following
On 25/07/2015 7:24 a.m., Alex Wu wrote:
> If I define 4 workers, and use the following way to allocate workers:
>
> if ${process_number} = 4
> //do something
> else
> endif
The "else" means the wrapped config bit applies to *all* workers and
processes of Squid except the one in the if-condition (
If I define 4 workers, and use the following way to allocate workers:
if ${process_number} = 4
//do something
else
endif
I leave other workers as empty after else, then we encounter this error:
FATAL: Ipc::Mem::Segment::open failed to
shm_open(/squid-ssl_session_cache.shm): (2) No such file or
