This is an additional safeguard against regressions of #1762

WHOA - sorry

We spilled into the client marker bit when reaching 1<<30

modifications relating to the object refcount issue.

is no sane way to refcount (dynamic) backends in relation to VCL
use at this point in the 4.1 release cycle.

Solve the problem, for now, by cooling dynamic backends off for a
minute before actually removing them.

Varnish 5 will have to look at proper refcounting of (all) VCL objects.

we need.

Send warm dynamic backends "COLD" event before deleting them.

with EINTR.

I suspect the underlying issue is that SIGCHLD is being sent
to a random thread and that happens to be the s1 thread on some
platforms.

Partially from minusf via github

Spotted by:	Dridi

previous commit.

Fixes: #1755

connection count.

Instead we mark the dynamic backends unhealthy with the status "deleted",
hide it from CLI displays, prevent new connections from being opened
and clean the backend up when the connection count goes to zero.

Radically different from patch from: Dridi

conversions between enum and text.

Based on patch from:  Dridi

There is potential for improvement in this whole
documentation build business of ours.

The amount of output does (did) not correspond with the importance of
this task. Now at least we'll see the warnings clearly.

I think it makes sense to ship a built HTML copy in
the tarball, as well as the RST sources.

The old cleanup code was a tad eager and made phk miss
his svg. Hopefully this way is a bit more future proof.

automake is our friend.

We might have to update some packaging files later on.
(and perhaps the git push hook.)

Partially from minusf via github