Re: [squid-users] --foreground vs -N

2019-09-18 Thread B. Cook
our interest in my question(s); greatly appreciated. On Wed, Sep 18, 2019 at 4:14 PM Alex Rousskov wrote: > > On 9/18/19 3:37 PM, B. Cook wrote: > > > this is /dev/shm with --foreground (no workers) > > > -rw--- 1 proxy proxy8 2019-09-18 10:30 squid-cf__metadata

Re: [squid-users] --foreground vs -N

2019-09-18 Thread B. Cook
Thank you for the response.. Confused what you mean.. this is /dev/shm with --foreground (no workers) root:/dev/shm # ls -al total 12 drwxrwxrwt 2 root root 100 2019-09-18 10:30 . drwxr-xr-x 17 root root 3120 2019-09-17 09:08 .. -rw--- 1 proxy proxy8 2019-09-18 10:30 squid-cf__met

[squid-users] --foreground vs -N

2019-09-18 Thread B. Cook
tl;dr: is there any functional difference between the two? Using runit to handle my squid processes. I have Observium graphing system information. My data/traffic is consistent In my run file I changed from squid -N to squid --foreground #!/bin/sh -e exec \ chpst -o 131070 \ chpst -e ./env \

Re: [squid-users] Crash: every 1-2 hour: kernel: Out of memory: Kill process (squid)

2016-12-14 Thread B. Cook
What does squidclient show? Get a trace going.. On Dec 14, 2016 11:52 PM, "Amos Jeffries" wrote: On 15/12/2016 6:24 a.m., n...@forceline.net wrote: > Eliezer, thanks for your reply. Guides: > http://wiki.squid-cache.org/Features/SslBump > http://wiki.squid-cache.org/Features/SslPeekAndSplice >

Re: [squid-users] dead gateway, not dead peer..

2016-06-22 Thread B. Cook
se try the request again.​ On Wed, Jun 22, 2016 at 10:45 AM, Amos Jeffries wrote: > On 23/06/2016 2:00 a.m., B. Cook wrote: > > ... > > > > What can I do about it? > > > > (thank you for working through understanding the problem..) > >

Re: [squid-users] dead gateway, not dead peer..

2016-06-22 Thread B. Cook
... What can I do about it? (thank you for working through understanding the problem..) On Wed, Jun 22, 2016 at 9:55 AM, Amos Jeffries wrote: > On 23/06/2016 1:25 a.m., B. Cook wrote: > > ​when the one of the proxies loses its internet connection.. the default > > route is

Re: [squid-users] dead gateway, not dead peer..

2016-06-22 Thread B. Cook
outside is dead and gone. That is what I am trying to fix.. When a cache_peer has a connectivity problem.. On Wed, Jun 22, 2016 at 12:46 AM, Amos Jeffries wrote: > On 22/06/2016 7:12 a.m., B. Cook wrote: > > On Tue, Jun 21, 2016 at 3:18 AM, Amos Jeffries > wrote: > > > >&

Re: [squid-users] dead gateway, not dead peer..

2016-06-21 Thread B. Cook
On Tue, Jun 21, 2016 at 3:18 AM, Amos Jeffries wrote: > > So you're trolling. The FAQ it is then: > > > > ​Thank you the response.. squid.conf (3.5.19 debian host 192.168.10.115) cache_peer

Re: [squid-users] dead gateway, not dead peer..

2016-06-20 Thread B. Cook
On Mon, Jun 20, 2016 at 4:04 PM, Antony Stone < antony.st...@squid.open.source.it> wrote: > > > Please answer the following questions: > > 1. How many squid servers do you have (in this setup)? > ​ I have three squid servers ​ > > 2. What are their IP addresses? > ​172.16.0.30/20 - Oasis, 172.16

[squid-users] dead gateway, not dead peer..

2016-06-20 Thread B. Cook
Looking for a second opinion.. I think this is beyond the scope of squid, but I figured I would ask anyway.. VZW FiOS link in one building (primary) and VZW FIOS link in a second building (secondary). the gateway for the primary link is sometimes unavailable.. squid is fine on both ends.. 0.30