There is currently no locking around temperature changes despite the
fact that it may be read outside of the CLI thread to make decisions.

In the case of a panic, instead of locking we simply make sure not to
perform an incomplete read of the pointer.

Conflicts:
	bin/varnishd/cache/cache_vcl.c

This will allow anyone with the Coverity scanner installed and our
authtoken to upload their own feature branch if they want to.

Main point is to get this out of the Jenkins job definition and into
something that is more developer accessible.

Doing my best to keep it /bin/sh compatible.

There are two timeout names where `timeout` is the prefix:

- timeout_linger
- timeout_idle

If it were up to me, they'd be called the other way around and according
to the documentation:

> `session_linger` has been renamed to `timeout_linger

If it were up to me, it would have been renamed to a self-describing
`session_linger_timeout` (wink wink, nudge nudge).

Typo spotted by scn.

Thanks, Dridi

Addresses question in #2038

Addresses question in #2038

The P macro is only ever called with one argument and Solaris cc
rightly emits E_ARGUEMENT_MISMATCH (yes, with the typo)

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