On Sat, Jul 3, 2010 at 11:16 PM, Alexander Staubo <[email protected]> wrote: > On Sat, Jul 3, 2010 at 11:04 PM, Per Buer <[email protected]> wrote: >> On Sat, Jul 3, 2010 at 7:59 PM, Alexander Staubo <[email protected]> wrote: >>> On Sat, Jul 3, 2010 at 7:01 PM, Flavio Torres <[email protected]> >>> wrote: >>>> Hi Alexander, >>>> >>>> Have you seen this thread >>>> http://lists.varnish-cache.org/pipermail/varnish-misc/2010-June/004358.html >>>> ? >>> >>> Yes. That threads seems to be about a different problem. >> >> I don't think so. Try it. > > I do think so:
There is only one place where SIGQUIT is used and that is where you're hitting it. I'd try to disable the whole check by setting the cli_timeout ridiculously high. If you have proper monitoring the risk isn't high. You might be having issues with your io scheduler (cfq can be a real disaster) or a bigger working set then your memory can handle (swap on Linux doesn't work very well). -- Per Buer, Varnish Software Phone: +47 21 98 92 61 / Mobile: +47 958 39 117 / skype: per.buer _______________________________________________ varnish-misc mailing list [email protected] http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
