debugging:

Implement an upper limit for allocated memory, specify as:
	-smalloc,40M

Give the malloc allocator its own stats counters so we can see deeply
into what it does.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2629 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2628 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2627 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2626 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2618 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2617 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2616 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2615 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2614 d4fa192b-c00b-0410-8231-f00ffab90ce4

Two really bad ones in Vary processing, found by Arjan (noosius).

One isignificant one related to -b arguments being wrong,
found by FlexeLint after I taught it how to spot this kind of issue.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2613 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2612 d4fa192b-c00b-0410-8231-f00ffab90ce4

"Authentication" for this long without anybody noticing until now.

Mea Culpa.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2611 d4fa192b-c00b-0410-8231-f00ffab90ce4

string for the status code as found in RFC2616.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2609 d4fa192b-c00b-0410-8231-f00ffab90ce4

changelog entries, cleaned debian/rules.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2608 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2607 d4fa192b-c00b-0410-8231-f00ffab90ce4

(IOV_MAX < (HTTP_HDR_MAX * 2)) is equivalent to (IOV_MAX < (0 * 2)),
which obviously is never true.  Fixes #222.

Submitted by:	Jyri J. Virkki <jyri@virkki.com>


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2606 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2605 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2604 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2603 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2602 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2600 d4fa192b-c00b-0410-8231-f00ffab90ce4

possible for various modules to add cli functions so they can
be manipulated on the fly.

CLI_AddFuncs() registers a set of CLI functions.  We operate
with three lists: the ones not shown in "help" because the
manager already showed them, the normal ones and the debug
commands which are also not shown in a plain "help".

Move the registration of cli functions out to the code they
belong in: VCL, BAN and VCA.

Give VCA a real Init function, and have the cli function ("start")
initiate the acceptor thread which listens for incoming connections.

Split CLI_Init() into CLI_Init() and CLI_Run()



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2598 d4fa192b-c00b-0410-8231-f00ffab90ce4

in malloc'ed memory.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2597 d4fa192b-c00b-0410-8231-f00ffab90ce4

of overloading common cli function namespace "cli_func".


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2596 d4fa192b-c00b-0410-8231-f00ffab90ce4

not have to grope around in the cacher's data structures.

Whenever the manager gets a CLI command it does not understand, it
will pass it to the cacher process, if it is running.

This complicated "help" a little bit, because we want to show the
combined commands of the manager and cacher.

Since we're dealing with help anyway, hide undocumented debug
commands from it.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2595 d4fa192b-c00b-0410-8231-f00ffab90ce4

with '-'.

Remove header line.

If argument is not found, return CLIS_UNKNOWN.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2594 d4fa192b-c00b-0410-8231-f00ffab90ce4

tiny braino.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2593 d4fa192b-c00b-0410-8231-f00ffab90ce4

Noticed by:	Jyri J. Virkki <jyri@virkki.com>


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2592 d4fa192b-c00b-0410-8231-f00ffab90ce4

entries, a 'c' for client-related log entries, and a ' ' for everything
else (CLI Ping for instance).  This makes it hard to process logs with
awk or similar tools, since the number of columns varies.  Therefore,
change the character used for non-backend-or-client log entries to '-'.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2591 d4fa192b-c00b-0410-8231-f00ffab90ce4

Reduce SHM mutex contention further, by only holding lock over
reservation of space, and do the copying from workthread buffer
to shm buffer efter we let go of the mutex.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2590 d4fa192b-c00b-0410-8231-f00ffab90ce4

Debian packaging: Move control file "docs" to "varnish.docs" for consistency, add HTML changelogs from the doc/ directory to the packaging

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2588 d4fa192b-c00b-0410-8231-f00ffab90ce4

Debian packaging: Fix syntax error in varnishlog init script, and set correct variable in defaults file. Add clarifying comment for variable

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2586 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2583 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2582 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2580 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2577 d4fa192b-c00b-0410-8231-f00ffab90ce4

Ignore SIGPIPE, otherwise varnishreplay will stop as soon as varnishd starts
overflowing.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2576 d4fa192b-c00b-0410-8231-f00ffab90ce4

-s, this allows varnishlog to be used to extract part of a log file, or
partition a log file into smaller sections.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2575 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2572 d4fa192b-c00b-0410-8231-f00ffab90ce4

fd has finished, flush the previous request with an additional line to note
that the request was interrupted.

This is usually a symptom of the child dying midway through the first
request.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@2569 d4fa192b-c00b-0410-8231-f00ffab90ce4