private pointers.



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

Will describe evil details in sphinx docs in a moment.



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

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

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

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

Don't try to trim a storage segment we filled completely.

Fixes: #776



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

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

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

new structs are added.



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

This allows us to collect lock collision information without
incurring the overhead of VSL, which should give more relevant
and precise information.



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

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

Fixes: #769


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

Fixes: #768



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

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

Fixes: #762


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

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

client connection:

	VOID set_ip_tos(INT)

Fixes:	#773



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

A procedure is simply a function which returns VOID.



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

in expressoins.



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

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

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

attempted imported more than once.



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

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

a default.vcl file we know will exist.



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

fleshed out the directors a bit more. unsure about if the hash/client dir take the retries parameter

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

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

We want to access files in the build directory, not the source
directory.


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

The effect of this is that the root object in the binheap could be
wrong and thus hold the expiry thread hostage, even though other objects
were ripe for expiry. 

This would show up as inflated obj/objcore/objhdr counts, but have no
other deleritous effects.

Detected, conclusively, by:	sky


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

python 2.4 (which RHEL5 has, at least) doesn't have str.partition, so
implement it as a compatibility function.


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

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

Thanks to DocWilco for spotting this.


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

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

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

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

dlclose() objects compiled with gcov support.  (Search "atexit dlclose" for
details).



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

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

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

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

Add stats counter to keep track of how many vmods are on the list
mostly so the testcase can see that it works.



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

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