[squid-dev] [RFC] Fix shared memory initialization, cleanup. Ensure its usability.

[Alex Rousskov]

On 12/09/2015 02:19 PM, Amos Jeffries wrote:

>> Questions: Should we add a configuration directive to control whether
>> mlock(2) is called? If yes, should mlock(2) be called by default?
>> Should mlock(2) failures be fatal?

> My answers are no, yes, yes. Since this is a startup thing squid.conf
> post-processing is probably too late.

Not sure I understand. Shared memory is not allocated until _after_ we
parse squid.conf. The allocation code needs to know how much to allocate
and that depends on squid.conf. mlock() is a part of the shared memory
allocation code...

FWIW, in my description about startup delays, "startup" is everything
that happens before Squid is ready to handle requests.


Thank you,

Alex.