duplicate counters consistent on reloads.

Add a test case for this.

Add a section on bans and offline silos in the docs.

be recognized as such on reload

the header, not 0).

Add a test case for reload of truncated bans.

Fixes: #1266

This isn't really functional right now, due to the log record changes,
but it will allow you to specify -b again and you can have a different
format for backend requests than for client requests.

accept-sockets can actually be bound before we muck about with
daemon() or SHM files.

Belived to be implicated in #1262

Fixes #1259

namespace for vmod.

once I get the other compiler to cope too.

This snapshot is committed to solicit feedback, so please do :-)

features.

As per discussion at the Varnish dev meeting, seeing Cache-control:
no-cache (and friends) now disable caching by default.  As a twist, we
respect Surrogate-control if that is present, in the default VCL.

Fixes: 1124
References: 477

If we don't add -c and -b in there, varnishlog will print all
transactions that aren't associated with a session.  That is likely to
not be what the user wants.

Fixes: #1071

poll can return EINTR, so we need to handle that.

Fixes: #1166

Fixes #1198

good, but at least it belongs here.

Fixes	#1255

Eliminate SIGCHLD usage, it's icky, at best, when we have other
child processes (See #1256)

Instead of reaping the child on SIGCHLD, we do it explicitly,
and there is now a 10 second wait to give the child a chance to
shut down gracefully, before we take a bat to the kneecaps.

More work may be warranted, but I want to get some feedback on
this bit first.

Fixes	#1256

Add a read-method to http_conn, and use it from all VFPs, which
should be protocol agnostic.

from HTTP1 specific functionality.

resp.*

Submitted by: jonathan.huot@thomsonreuters.com

	tmo can become negative if timeout_idle gets changed on the fly
	or when the rtc jumps

It does not make any kind of sense to build a vmod as a static
library, so tell libtool to only build a shared one.

parallel builds (make -jX) failed sporadically for the first compilation
(before dependency tracking information was available) due to the race
with python building vcc_if.h

From 8e2751a28b7cb6331b386fbf6e1a7b1bdeafb4b7 Mon Sep 17 00:00:00 2001
From: Nils Goroll <nils.goroll@uplex.de>
Date: Wed, 9 Jan 2013 20:46:13 +0100
Subject: [PATCH] proper dependencies for vmod automake

parallel builds (make -jX) failed sporadically for the first compilation
(before dependency tracking information was available) due to the race
with python building vcc_if.h

Reduce warning noise from autoconf
Make automake happy
Pull in current ld-version-script.m4 which fixes the issue documented here:
https://lists.gnu.org/archive/html/bug-gnulib/2010-08/msg00198.html

From c24a91405479e7e5bd2633173cf5a24eabbd75fc Mon Sep 17 00:00:00 2001
From: Nils Goroll <nils.goroll@uplex.de>
Date: Wed, 9 Jan 2013 19:45:14 +0100
Subject: [PATCH] make autocrap(tm_phk) tools happy

Reduce warning noise from autoconf
Make automake happy
Pull in current ld-version-script.m4 which fixes the issue documented here:
https://lists.gnu.org/archive/html/bug-gnulib/2010-08/msg00198.html

complex future world.

to pave the way for sharing some code on client and backend side.

it is a VBO function which extends the busy object with data which
streaming clients can access.

Name it VBO_extend() instead and move it home to the rest of the
VBO functions.

of 0, 1 and 2.

This makes varnishncsa behave the same way as varnishlog, and prevents
overly large memory allocations if it should see a bogus fd (shmlog
overrun?).

XXX: This will not fix varnishncsa for current trunk, as that is using
XIDs instead of FDs breaking some functionality in the tools. This
will be handled in the API rewrite.