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

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

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

this object has seen.

Idea for prefetching being used as workaround for #310 



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

A "unsigned *" is not the same as a "unsigned"



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

It'll typically be used in a manner similar to:

    if (! backend.healthy) {
        error 500 "Backend sick!";
    }


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

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

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

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

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

fixes #305



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

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

Try to nail r297 again



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

on redhat.



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

If you attach gdb to a running varnish child, then when you tell it to continue it will abort if assertions are enabled due to poll returning with EINTR.

This just re-enters the loop.



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

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

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

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

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

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

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

- Added the LICENSE file to the libs-devel package
- Moved make check to its proper place


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

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

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

When starting as root and then setuid-ing, we need to set the dumpable
bit to get core dumps on Linux.  Do so.


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

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

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

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

We're not binary compatible, so bump soname.  Closes: #293


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

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

will make at getting a backend connection.  By default it tries as many
times as it has members.



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

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

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