It's no longer used anyway, and was already called via the generic
VUT_Arg function.

We don't need an indirection in a separate C file per VUT.

- Revert to previous trusty image (ref. google/sanitizers/issues/837)
- Switch to xcode9 on osx
- Scaffolding to get the sanitizer job using clang 5.0
- ASAN: Disable stack protector
- ASAN: Ignore sigsegv and sigbus

Missed in 32877991.

This still needs more TLC! Please feel free to continue...

It got lost during the new world order megacommit
74328de8

varnishd writes its pids to vsm segments for vsm clients to
determine if varnishd processes are alive.

When running varnishd and vsm clients in different containers, the
pid information has no relevance and may even be ambiguous across
name spaces.

Setting the environment variable VSM_NOPID for vsm clients disables
use of pid information.

Patch by phk

indicated the process was present at one point.

Fixes #2420

Fixes #2419

accordingly.

If somebody has time to push varnishstat in curses mode though the
paces and check that everything works I'd appreciate it.

The general rule is that if varnishd is started as root, you need
to be root or in group "varnish" to access the shared memory.

Fixes	#2419

Helped by: PC-Lint-Plus-RC2

Fixes	#2417

VSC neatly on top of VSM.

Closes #2406
Refs #2157