Conflicts:
	bin/varnishd/cache/cache.h
	bin/varnishd/cache/cache_ws.c

The parsing still requires some TLC but this does not make it any
worse so let's get this in first.

Prompted by and ideas from github::xcir via #2077.

Change some tests to use the new parameter and more coverage.

be found are options to "shell".  Deprecate err_shell.

Structure output to always be prefixed by "shell" since we're running
at the top level.

Also prefix commands with "exec 2>&1 ;" to join stdout+stderr by default.
This still doesn't cover the shells stderr in case of bad shell syntax,
which is annoying, but not worth fighting for right now.

Otherwise the backend might see multiple Connection entries.
Fixes #2337.

In the section related to make test, the sentences were a bit hard incorrect. I've corrected it.

Fixes #2329

This is a cherry-pick of 3271c51e that
fixed the issue for Varnish 3.0 since it wasn't a problem in the 4.1
series then. This is only a back-port of the regression test since the
referenced commits already fixed the regression.

Refs 5e4d6c84
Refs 9f422620
Refs #2069

Fixes: #2313

This is a back port of f1741d99 from master.

Conflicts:
	lib/libvmod_std/vmod.vcc
	lib/libvmod_std/vmod_std.c

This should help diagnose #2253.

already failed.

Fixes #2301

Conflicts:
	configure.ac
	varnish.m4

It shares a lot of parsing infrastructure with log records, but doesn't
support the taglist syntax. Only a verbatim `vxid` token can be used as
the LHS, and only integer operators are supported.

There was a missing bracket that I fixed but forgot to amend the
commit. Fixing with this one.

By rounding Age down, we make sure Age < max-age while the object
is fresh. Otherwise, we can prematurely get Age == max-age and Varnish
will calculate that as a 0s TTL and create a pass scenario.

Conflicts:
	bin/varnishd/cache/cache_req_fsm.c

This lets you set environment variables in a test case.

Usage is

    setenv "FOO" "bar"

which will set FOO=bar if FOO does not already exist.

There is also an optional '-force' argument, which will overwrite the
current variable if already set:

    setenv -force "FOO" "baz"

The force argument corresponds to passing a non-zero third argument to
setenv(3).

It uses `explicit_bzero` when available and falls back to `memset`
otherwise.

Conflicts:
	configure.ac

VBE_Poll would not advance to test the next backend on the cooling
list when the backend's n_conn is non-zero. This would create a
spinlock effect, causing delays that could make the master kill the
child because of CLI timeout.

Fixes: #2295

The child expects mgt to be consistent in its VCL state changes,
e.g. not ask the child to 'use' a VCL that isn't warm. Not doing so
will cause the child to assert (see asserts in
cache_vcl.c:ccf_config_use). This could trigger because the mgt
erranously would set its recorded temp regardless of the child's reply
in mgt_vcl_setstate.

This patch changes it to only record the new temp in mgt if the child
replied success. If the child isn't running the new temp is always
recorded.

Slightly update v00044.vtc test case to reflect the need to update the
state before restarting the child.

Ref: https://github.com/varnishcache/varnish-cache/pull/2273

Newly loaded VCLs didn't get their go cold timer set even when they
were set to auto, causing them to never go cold automatically.

Fixes: #2270

Conflicts:
	bin/varnishd/mgt/mgt_vcl.c