Spotted by: Coverity

Spotted by: Coverity

Spotted by: Coverity

Spotted by: Coverity

Spotted by: Coverity

Found by Coverity

we know what we're doing.

Spotted by: Coverity

Spotted by: Coverity

Spotted by: Coverity

Spotted by: Coverity

The code got word sizes confused, and failed to allocate a proper
buffer based on the word size. Make the code use word sizes in local
variables for clarity and make sure that the allocation routines get
byte sizes.

Spotted by: Coverity

Spotted by: Coverity

open VSM connection

Use VTIM_real instead of VTIM_mono for mgt uptime so that the time
won't stop counting when the computer is suspended.

The query language has it's own doc page in varnish-query

Teach the parser how to read a comma separated list of tag globs,
rather than having the ',' character be recognised as valid for
barewords.

Having the query input to the utils be cmd line args leads users to
believe that the args are interpreted as tokens themselves. The parser
doesn't see each argument as a token, but instead makes one string
from all the arguments. This would cause quoting issues.

By having the query expression be an option instead, it becomes
clearer that the input is one string only, and any quoting when
constructing an expression from some other input is left to the user.

A vtx_diag log record could realloc the memory buffers while
processing a vtx, causing ptrs to previous memory to be still used.

Fix this by having generated log records be malloced and kept on a
separate list, which is always reported first on a reset cursor.

Fixes: #1351

This to silence valgrind errors

Now that VSL records are null-terminated, it is safe to run sscanf
without copying to a temporary null-terminated buffer.