On 03/07/2016 04:49 AM, Silamael wrote: > We're updating to Squid 3.5 under OpenBSD and have some issues with the > apparently new shared memory behavior: > 1. Squid always creates three shared memory files and does not remove > these on shutdown > 2. As we're running multiple complete different configuration on the > same machine on different ports, the shared memory files collide and > Squid does not start up properly If Squid creates shared memory segments without you using SMP features, it is a Squid bug. I recall fixing one such bug in Squid v4/trunk recently. Perhaps it exists in v3.5 as well. I recommend filing a bug report while specifying exactly which files are being created. If Squid does not remove shared memory segments on shutdown, it is a Squid bug. I recall fixing one such bug in Squid v4/trunk recently. Perhaps it exists in v3.5 as well. I recommend filing a bug report while specifying exactly which files are left behind. FWIW, Squid v4 supports the "-n" command line option to assist with running multiple instances on the same box (with or without using SMP features). I do not remember whether v3.5 supports that as well but it may. I do not remember whether "-n" support extends to shared memory segment names but it should. Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
