Ideally we could just reset it, but other in-fsm-state uses of this
workspace is allowed, so we cannot know for sure that the workspace
is empty when we begin.

to keep it light and small, so we forbid any long-term usage an detect
leakage with this assert.

Fixes	#1206
Found & Fixed by:	DocWilco

Found & Fixed by:	Federico G. Schwindt
Fixes #1212

0ad568 should never have been pushed.

This reverts commit 4f6eaa24.

ban() was previously not in bold on the man page. Turn it into two
separate entries with separate descritions to fix that.

the strings we get from the libvarnishapi functions are not
necessarily null-terminated, so avoid using str* functions on them.

Thanks to lampe for the patch.

Fixes #1115

Fixes	#1211

Thanks to:	Federico G. Schwindt

POLLHUP is always checked for, and is output-only on Linux and OSX, so
avoid putting it in the list of events we check for.

architectures.

NB:  VMOD writers need to review/revise use of the INT type.

Fixes #1204

way any stevedore interested in new bans can request to be notified
(not just the persistent).

Also report dropped bans to the stevedores.

signal background threads to stop in preparation for the coming close
callback.

allocation calculations.

This then also breaks the previous expectation that cur_seg would
always be non-NULL. Change the code to take this into account.

Fixes: #1146

smp_copy_signspace() will copy the sign data of one space onto another.

smp_trunc_signspace() will truncate the signed space to len bytes and
resign the space.

growing signed data structures.

build happy on FreeBSD.

This should not have any impact on the "normal" deliveries, as these
will as before be done through a single writev operation.

For deliveries involving chunked encoding (e.g. ESI or gunzip), this
should prevent an unnecessary delay where the Nagle algorithm kicks in
on the end-chunk write. This should give higher throughput and better
utilization of a single connection, especially for clients not doing
pipelining.

buy 512TB ram to run Varnish on ppc64.

Separate out the text describing the storage backends so it can be resued in both the man page and users guide