That seems to have done the trick! I've only tested for about half an hour so far, but the memory usage is quite stable so far.
Thanks! Bryan On Mon, Aug 22, 2011 at 2:24 AM, Poul-Henning Kamp <[email protected]> wrote: > In message <[email protected]>, "Poul-Henning Kamp" writes: >>In message >><cadafl_hw_y69f6sqxpke8dvut9mckcnd0ghy_qr1vbonqvz...@mail.gmail.com> >>, Bryan Stillwell writes: >> >>>I believe I'm running into the problem mentioned in this bug report: >>> >>>https://www.varnish-cache.org/trac/ticket/953 >>> >>>I've tried the following fix, but it doesn't appear to fix the problem: >>> >>>https://www.varnish-cache.org/trac/changeset/beb0c5b1f4f49d711822e90ca73d69bbed683a71 >> >>I'm still trying to find the root cause of this issue. > > Update: I think I just nailed it, please try -trunk. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [email protected] | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
