Just upgraded squid to 4.1, however if I enabled shared_memory_locking I failed to start squid:
"FATAL: shared_memory_locking on but failed to mlock(/squid-tls_session_cache.shm, 2101212): (12) Out of memory" How do I know how much memory it is trying to mlock? is 2101212(~2MB) the shm size of not, any way to debug/looking-into/config this size? Again I disabled cache etc for a memory restricted environment, also used the minimal configuration with a few enable-flags, in the meantime I want to avoid memory overcommit from squid(thus mlock) Regards, Gordon
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
