Re: [squid-users] 3.5.8 Arm7 socket permissions

I have fixed this issue. The Kernel Image I am using is configured with *CONFIG_ANDROID_PARANOID_NETWORK =y * changing this to *# CONFIG_ANDROID_PARANOID_NETWORK is not set

Re: [squid-users] 3.5.8 Arm7 socket permissions

HI Thanks again for having a think about this. with debug options 78.2, I get the following 2015/10/29 20:43:11 test| Starting Squid Cache version 3.5.8 for arm-poky-linux-gnueabi... 2015/10/29 20:43:11 test| Service Name: squid 2015/10/29 20:43:11.918 test| 78,2| src/dns_internal.cc(1534) d

Re: [squid-users] 3.5.8 Arm7 socket permissions

On 29/10/2015 11:11 p.m., Darren Breeze ML wrote: > Hi > > Thanks for the reply. > > Libcap2 is in the build, but the build is for an Arm7 and the rootfs is > read only. Anything that needs write access I have moved to a ram disk > and symlinked it back into the expected place during the build pr

Re: [squid-users] 3.5.8 Arm7 socket permissions

Hi Thanks for the reply. Libcap2 is in the build, but the build is for an Arm7 and the rootfs is read only. Anything that needs write access I have moved to a ram disk and symlinked it back into the expected place during the build process. There must be something else in the OS standing in th

Re: [squid-users] 3.5.8 Arm7 socket permissions

On 29/10/2015 11:16 a.m., Darren Breeze ML wrote: > Hi all > > I have built squid 3.5.8 with yocto to run on an arm 7. > > This build of the OS seems to have different permissions for processes > opening sockets. THe DNS routine fails to open a socket with the > following error > > root@test:~#

[squid-users] 3.5.8 Arm7 socket permissions

Hi all I have built squid 3.5.8 with yocto to run on an arm 7. This build of the OS seems to have different permissions for processes opening sockets. THe DNS routine fails to open a socket with the following error root@test:~# 2015/10/28 22:07:43 testing| Starting Squid Cache version 3.5.8