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

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

tree we are testing in.



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

${varnishconfdir} respectively.



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

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

definition for __FreeBSD_version.



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

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

Fixes: #760


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

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

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

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

It correctly identifies that the .list option is currently out-of-sync with
the rest of VCC and needs to be adjusted. It's on the todo.



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

Introduce req.hash_always_miss (force cache miss) and req.hash_ignore_busy (ignore busy objects) variables available in vcl_fetch.



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

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

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

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

a new VCL program initializes of finishes.

This also gives access to a per-VCL private void* which can be passed
as a hidden argument to the member functions.

If modules hold any global state, they should use the meta function to
keep track of when the last VCL program finishes and clean up their
internal global state then.



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

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