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

        backend default {
                .host = "127.0.0.1";
                .port = "9080";
                .max_connections = 100;
        }

will limit the simultaneous TCP connections to this backend to 100.

Stats counter backend_busy == "Backend connections too many" tells
how often we have hit this limit for a backend.



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

polled as unhealty.

This technically makes Varnish 2.0 "feature complete", but some further
polishing is to be expected.



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

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

First step in activating backend polling:  Do not attempt to open
connections to a unhealthy backend.



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

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

Fixed an error in the argument passing from the init script. Added some more info text to the stop action.

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

have the directors provide that.

Entirely a no-op, apart from a bugfix that just would screw
you even more (than "totally") if socket(2) should ever fail.



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

Submitted by:	ingvar
Fixes:		#298



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

consistently.

Fixes #297



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

also.



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

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

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

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

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

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

connect to, but a connection to a backend, this makes it possible
for the directors to choose another backend, if connection to the
first backend fails.



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

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

we actually need to get a filedescriptor to the backend.

This also makes it evident for vcl_pass{}, vcl_pipe{} and vcl_miss{}
if the client sent a Host: header or not.  Previously these functions
saw the default Host: header.



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

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

IANA has reserved the 198.18.0.0/24 network for Network Interconnect Device
Benchmark Testing which vaguely fits what we are doing.  Use that
instead of 127.0.0.2 since the latter works fine to bind to on Linux
(at least).


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

When testing synthetic error page caching, make sure we connect to
:9080 rather than the default :80 since the machine might well have an
httpd running already.


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

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

Don't look for umem on FreeBSD, which have dummy stub version for
dtrace or ZFS compatibility.

Generally restrict probes for Solaris specific stuff to when we
run on solaris, no need to make configure slower than it is.

Don't pretend we can get anywhere without poll(2) we use it for
lots of things:  Remove #if conditionals around poll-acceptor.

Sort a couple of lists, before they get too unsorted.

Submitted by:	Theo Schlossnagle



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

really check anything yet, because we lack the stats counters to test.



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

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

with its header around.

Found and nailed by:	Adrian Otto <aotto@mosso.com>



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

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

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

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

traffic fares.  Problems seen there could be caused by all sorts
of special circumstances (bad PHP, weird headers from client etc)
and is not indicative of the backends health.



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

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

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

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

probe requests.



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

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

paramters.

Log each polls result in the SHMlog



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

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

.window is how many of the latest polls we examine.
.threshold is how many must have succeeded for the backend to be healthy.

	.window = 40;
	.threshold = 30;
		// Thirty of the last fourty polls must have succeed.

	.threshold = 4;
		// The last four polls must have succeeded.

Default values:
	.window = 8;
	.threshold = 3;



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

When an -expect fails in varnishtest, loop for up to a second since stats sometimes takes a little while to update


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