rather than the values from pkg-config only. CLAGS and LIBS
may contain important generic compiler / linker flags for this
platform.

Fix an issue where the new timestamp was set without locking.

Spotted by: Coverity

Refs #2008

Spotted by Foxik on #varnish @ irc.linpro.no.

Ref: #2008

For match_tag == SLT_Timestamp, we'd miss a match otherwise.
Add the missing /* FALLTHROUGH */

This reverts commit 97bfb002.

Conflicts:
	bin/varnishhist/varnishhist.c

If a log transaction is parsed that don't contain timestamps
(e.g. they are filtered in varnishd), then this would cause a NULL
pointer dereference.

Fix an issue where the new timestamp was set without locking.

Spotted by: Coverity

Also spring some VUT_Error() love.

Conflicts:
	bin/varnishhist/varnishhist.c

Thx @fgs

Thx @fgs

Conflicts:
	bin/varnishhist/Makefile.am

This is particularly useful when replaying vsl files (-r option).

The new -B option specifies a time factor limiting the speed at which
the log is being read. It can also be halved/doubled using the < and >
keys at runtime.

Conflicts:
	bin/varnishhist/varnishhist.c

Actually implement the documented -p option

Make the update delay a double to allow update frequencies of less
than a second.

Add + and - keys to the curses interface to update the refresh
frequency while running.

Show update frequency in the top line.

... for the standard backend timestamps and size.

Conflicts:
	bin/varnishhist/varnishhist.c

In the usage section of varnishstat, some non-literal options were not
caught by the backport.

In usage/documentation, mark those options with <> which are not a
literal string, but rather a placeholder for some value.

Conflicts:
	bin/varnishstat/varnishstat_options.h

This is an adaptation of b2c18706 by Federico G. Schwindt.

Previously you needed an empty argument (''), which didn't play very
well along sysv init scripts and was not documented. Now both "none"
and the empty argument work, but an extra warning is echoed if the
empty argument is used.

The documentation only mentions "none" for disabling the secret, since
this is the only way of doing it in the next version.

Fixes #2007.

fix #2027

In addition to harcoded features in varnishtest, this opens a window for
out-of-tree uses of the test framework to skip test cases if an external
component (a database system, OS-specific capabilities, an environment
variable, a library, etc) is missing.

This feature takes an extra argument, a command-line that must exit with
a zero status. Complex feature testing can nicely be wrapped in scripts
at the user's discretion:

    feature cmd "my --command=line"

If the test is skipped, it is logged as:

    **   top   0.0 === feature cmd "my --command=line"
    *    top   0.0 SKIPPING test, missing feature: my --command=line

If the command-line is missing, it is logged as:

    **   top   0.0 === feature cmd
    ---- top   0.0 Missing the command line

There are some changes in master that need tlc before backporting.
This is one of them.

We will need it if the body was consumed due to a call to
std.cache_req_body (VRB_Cache).

Analysis and test by daghf.

Fixes #1881.

Conflicts:
	bin/varnishd/cache/cache_req_fsm.c

For some (out of workspace or stevedore allocationi failure) errors
VFP_Close would fail to be called when ending up not retrying the
fetch. This would then potentially leak VFP entry context data like
gzip buffers. Fix this by always calling VFP_Close() when changing
fetch state when VFP_Open() has been called.

Also VFP_Close() would for some retries be called twice, causing
double accounting log records print out. This happens when a late
error is caught and streaming is disabled, allowing a retry to be
attempted. Fix this by not unconditionally calling VFP_Close() in the
error state.