dumps. What other
information would be useful in diagnosing and fixing
these issues?
Cheers,
Tim Kientzle
==
1) Varnish repeatedly died due to SIGSEGV:
child (2816) Started
Child (2816) said Closed fds: 4 7 8 10 11
Child (2816) said Child
This is a very strange comment. If Varnish requires a
particular sequence, it should implement its own. If
it requires particular statistical properties, it should
test for those, not test for a specific sequence.
Tim
On Jan 8, 2009, at 2:12 AM, Tollef Fog Heen wrote:
Another approach is to simply use a small bit of Javascript. It's
easy to test for the existence of the cookie in Javascript and
set that text conditionally.
Then you have only one copy of the page to be cached.
The problem with the approach you've outlined here is
that other downstream caches
I'm trying to just run a plain-vanilla varnish so I can see it running
before I start mucking with configuration.
But I'm not having much luck:
$ uname -a
Darwin tbkk.local 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep 3
11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386 i386
$ sbin/varnishd
Ah... It seems to work if I omit the -d option.
Tim
On Nov 12, 2008, at 11:11 AM, Tim Kientzle wrote:
I'm trying to just run a plain-vanilla varnish so I can see it running
before I start mucking with configuration.
But I'm not having much luck:
$ uname -a
Darwin tbkk.local 9.5.0 Darwin
Under certain circumstances, I want to inspect the body of a
POST request at the proxy cache.
It don't see any hooks for this in the current Varnish 2.0.1,
but I've skimmed the source and it looks feasible:
* I'll need code to actually read and store the POST body in memory
(including
:
In message [EMAIL PROTECTED], Tim
Kientzle wri
tes:
* I'll need code to actually read and store the POST body in memory
(including updates to the PASS handler and other places to
use the in-memory data when it's available)
We sort of have this as point 15 on our shoppinglist:
(http
