[squid-dev] To make squid works in snap world.

Gary Wang gary.wang at canonical.com
Fri Mar 17 08:05:09 UTC 2017

On Fri, Mar 17, 2017 at 7:40 AM, Alex Rousskov
<rousskov at measurement-factory.com> wrote:
> On 03/16/2017 05:30 PM, Gary Wang wrote:
>> On Thu, Mar 16, 2017 at 2:49 AM, Alex Rousskov wrote:
>>> On 03/15/2017 11:03 AM, Gary Wang wrote:
>>>>        In snap world, only the following name pattern is allowed
>>>>             /dev/shm/sem.snap.@{SNAP_NAME}.*
>>>>        not
>>>>             /dev/shm/snap.@{SNAP_NAME}.*
>>> That statement, if
>>> true, sounds like a snap bug, but, fortunately, it has no significant
>>> effect on the proposed argument sketch.
>>    A: It's not a snap bug, actaully.
>>       It's been confirmed and verified that only the following name
>>       pattern is allowed in snap world.
>>        /dev/shm/sem.snap.@{SNAP_NAME}.*
> How is "forcing an application that does not utilize semaphores to use
> sem.* as a filename prefix" is not a bug is beyond me, but this snap
> issue classification (bug, feature, problem, whatever) is not important
> for Squid. Once you make the filename prefix configurable, any prefix
> would work, including the weird one that snap apparently insists on.
   A: Yes, I think that's the reason why I submit the MP to support configurable
       prefix filename.
       Thanks for your comment Alex.
       Meanwhile, I made another change to keep new DEFAULT_IPC_PREFIX
consistent in src/ipc/Port.cc file.
       Could you guys help review the MP?


> Thank you,
> Alex.


More information about the squid-dev mailing list