Rename VSM_FOREACH_SAFE as it isn't really safe in the vqueue sense,
and removing chunks from the VSM from the client library isn't
applicable anyway.

Make the VSM chunk marker sizes defines.

Check for shm open in VSM__itern

Revisit logic of VSM__itern: Make sure that the VSM_fantom is either
changed to the next, or not changed at all.

Add comments.

Keep copies of class, type and ident in VSM_fantom, and use these when
revalidating fantoms.

Do a proper VSM_Open in varnishstat

Add a VSM_ResetError function

Differentiate between missing HEAD marker and zero alloc sequence. The
latter is an indication Varnish isn't running, the former a corrupt
file.

Fix newline on diag messages for consistency.

Fix return value check inversion bug on stat call in VSM_Abandoned()

Don't assert on VSM_Open on an already open VSM. Report success instead.

segment.

The API will use this counter to check for abandonment.

Make use of the SHM age attribute in VSM_Abandoned.

This gives a less expensive way (without doing stat syscall) to check
for abandonment. If there's been more than 2 seconds between calls to
VSM_Abandoned and the age attribute hasn't changed in between, the
stat on the file will be performed to see if the SHM file has changed.

VSM_Abandoned will be the standard way to check for SHM changes in API
utilities, and when it returns true, the application is supposed to
call VSM_Close and then VSM_Open to reopen the SHM file.

Update Makefile.am in various places for build

Format: <type> <parent-vxid>

Add SLT_End records at the end of all vxid transactions.

Add SLT_Link records whenever one initiates a new child transation.
Format: <type-of-child> <child-vxid>

This is used by VSL api to form structured log output.

process uptime counter.

Basically the backend can drop the reason (OK) when responding to
a probe without Varnish declaring the backend sick.
Reported by astrosti on https://www.varnish-cache.org/forum/topic/961

first one created.  I would have skipped #0 if it was me...

bereq.* rather than the req.*, since that's what the backend saw.

only pass req to FetchHdr if we intend to send the body over.

Change args to http_FilterReq() to lower level.

After the purge, you will end up in vcl_purge{} from where it will
(at some future date) be possible to order a fresh fetch of the
object.

Doing purge from vcl_recv{} solves half of the object existence
problems in vcl_lookup{}.

	return (error(status_code [ , response_string ]));

next method we'll end up in.

Fixes #1281

We may want a better way to return synthetic objects from
vcl_backend_reponse{}, it looks a bit clumsy in the vtc's so far.

fix the bug (category: "How did _that_ ever work") this uncovered.

and does nothing to make the tests objective any clearer.

difference in any way.

from req.