Re: [squid-users] Survey on assertions: When the impossible happens

2016-03-01 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 01.03.16 23:37, Alex Rousskov пишет: > On 03/01/2016 03:55 AM, Eray Aslan wrote: >> On Mon, Feb 29, 2016 at 09:43:09AM -0700, Alex Rousskov wrote: >>> Q2: Your Squid is asserting every 5 minutes. There is no [working] Squid >>> version you can sw

Re: [squid-users] Survey on assertions: When the impossible happens

2016-03-01 Thread Alex Rousskov
On 03/01/2016 03:55 AM, Eray Aslan wrote: > On Mon, Feb 29, 2016 at 09:43:09AM -0700, Alex Rousskov wrote: >> Q2: Your Squid is asserting every 5 minutes. There is no [working] Squid >> version you can switch to. Your network topology does not allow you to >> bypass Squid. Until the bug is fixed, w

Re: [squid-users] Survey on assertions: When the impossible happens

2016-03-01 Thread Eliezer Croitoru
Hey Eray, Indeed all of these are good and sysadmins should be able to handle them but.. in specific cases it's not easy. The cases I know about are: - SAT links (slow or costly) - Sensitive acl\security systems - Very low quality distance wireless links In the case of ACLs system bypass or br

Re: [squid-users] Survey on assertions: When the impossible happens

2016-03-01 Thread Eray Aslan
On Mon, Feb 29, 2016 at 09:43:09AM -0700, Alex Rousskov wrote: > Q2: Your Squid is asserting every 5 minutes. There is no [working] Squid > version you can switch to. Your network topology does not allow you to > bypass Squid. Until the bug is fixed, would you prefer to see fewer > assertions in ex

Re: [squid-users] Survey on assertions: When the impossible happens

2016-02-29 Thread Marcus Kool
This is not really #4. It is an enhancement for any of the three options. IIRC, Squid even supported gdb stack tracing natively on some platforms (but a script would arguably be better, except for busy proxies that cannot be blocked for 2-4 seconds it takes to run that script). This already

Re: [squid-users] Survey on assertions: When the impossible happens

2016-02-29 Thread Amos Jeffries
On 1/03/2016 6:46 a.m., Alex Rousskov wrote: > On 02/29/2016 10:22 AM, Marcus Kool wrote: >> >>> * Choices. >>> >>> Overall, there are three options for handling an impossible situation: >>> >>> 1. Quit Squid process. This is what Squid does today in most cases. >>> When the impossible happens,

Re: [squid-users] Survey on assertions: When the impossible happens

2016-02-29 Thread Alex Rousskov
On 02/29/2016 10:22 AM, Marcus Kool wrote: > >> * Choices. >> >> Overall, there are three options for handling an impossible situation: >> >> 1. Quit Squid process. This is what Squid does today in most cases. >> When the impossible happens, you get a crash. Very predictable. >> No malform

Re: [squid-users] Survey on assertions: When the impossible happens

2016-02-29 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 29.02.16 23:22, Marcus Kool пишет: > >> * Choices. >> >> Overall, there are three options for handling an impossible situation: >> >> 1. Quit Squid process. This is what Squid does today in most cases. >> When the impossible happens, you get

Re: [squid-users] Survey on assertions: When the impossible happens

2016-02-29 Thread Marcus Kool
* Choices. Overall, there are three options for handling an impossible situation: 1. Quit Squid process. This is what Squid does today in most cases. When the impossible happens, you get a crash. Very predictable. No malformed/corrupted/misleading HTTP messages (some are truncated).

Re: [squid-users] Survey on assertions: When the impossible happens

2016-02-29 Thread Alex Rousskov
On 02/29/2016 03:44 AM, Eray Aslan wrote: > On Sat, Feb 27, 2016 at 10:56:53AM -0700, Alex Rousskov wrote: >> Q0: Do you think an admin should be able to control the choice among the >> three options detailed above? > Not really, no. But if you think it is not an undue burden for > developers, wh

Re: [squid-users] Survey on assertions: When the impossible happens

2016-02-29 Thread Eray Aslan
On Sat, Feb 27, 2016 at 10:56:53AM -0700, Alex Rousskov wrote: > There is an ongoing discussion about the best approach to handling > impossible situations among active Squid developers. Constructive > feedback from a Squid admin point of view is welcomed! There is no obvious right answer. I usua

Re: [squid-users] Survey on assertions: When the impossible happens

2016-02-27 Thread Amos Jeffries
On 28/02/2016 7:52 a.m., joe wrote: > right Asserts is the best choice for critical function im with you define "critical". It is not always obvious. > on that in the other hand some function its not critical to have > asserts just trace() or some other function to notify the cache log Now yo

Re: [squid-users] Survey on assertions: When the impossible happens

2016-02-27 Thread joe
right Asserts is the best choice for critical function im with you on that in the other hand some function its not critical to have asserts just trace() or some other function to notify the cache log for warning and do not halt just keep running its choice of what function need to have asserts

[squid-users] Survey on assertions: When the impossible happens

2016-02-27 Thread Alex Rousskov
On 02/27/2016 05:02 AM, joe wrote: > isn't better to use for kid1| assertion failed: store.cc:1890: "isEmpty()" > in store.cc line 1890 assert (isEmpty()); > insted replace it with VERIFY (isEmpty()); > assert force the program to halt that's why the restart happen > and its very bad wen squid