We're using varnish for a public site, works beautifully and handled
getting slashdotted gracefully -- many thanks!
We built it with zc.buildout which creates .../parts/varnish/install/
var/varnish/FQDN/... and others. In a recent update, I accidentally
blew away the .../var/varnish/FQDN
On Jun 2, 2008, at 11:19 AM, Poul-Henning Kamp wrote:
Yes, restarting varnish (completely: ie both manager and child
process)
should recreate it with no side effects.
Varnish doesn't spend long time on startup, so I would just get it
done and over with.
Just tried it on a QA server and
In message [EMAIL PROTECTED], Chris Shenton write
s:
What's the recommended way to re-create this directory? I'm assuming
restarting Varnish will re-create it but want to be sure.
Yes, restarting varnish (completely: ie both manager and child process)
should recreate it with no side effects.
Hello,
I have 2 machines running varnish which handles around 1000 requests per
second each and sometimes the machines will just stop responding to any
network communication. A coworker used wireshark to check the connection
and saw a whole lot of tcp retransmissions. Normally I would suspect
On Mon, Jun 2, 2008 at 7:57 AM, Chris Shenton [EMAIL PROTECTED]
wrote:
We have to fill out pounds of paperwork in order to take any outage on
a public server, no matter how small. Is there a way to restart
Varnish without any downtime -- to continue accepting but holding
connections until