err.no Git - varnish/commit

]> err.no Git - varnish/commit

author	phk <phk@d4fa192b-c00b-0410-8231-f00ffab90ce4>
	Wed, 2 Aug 2006 07:07:56 +0000 (07:07 +0000)
committer	phk <phk@d4fa192b-c00b-0410-8231-f00ffab90ce4>
	Wed, 2 Aug 2006 07:07:56 +0000 (07:07 +0000)
commit	89fc97cb6c8f763a271b1fe0d8915ccda1817372
tree	d998c6f0eca33821e45f3265d5e25dd06d0676e2	tree \| snapshot
parent	91bc5b06470ea6944af4419b6a01b118b6d2ca6c	commit \| diff

I have nothing but circumstantial evidence that libevent is involved
in the current stack corruption I see, but we might as well avoid
using it where we can:

Don't engage the eventengine when we talk to the backend, just call
read(2) directly.

git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@595 d4fa192b-c00b-0410-8231-f00ffab90ce4

Varnish, the HTTP accelerator

RSS Atom

varnish-cache/bin/varnishd/cache.h		diff \| blob \| history
varnish-cache/bin/varnishd/cache_acceptor.c		diff \| blob \| history
varnish-cache/bin/varnishd/cache_fetch.c		diff \| blob \| history
varnish-cache/bin/varnishd/cache_http.c		diff \| blob \| history
varnish-cache/bin/varnishd/cache_pass.c		diff \| blob \| history