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

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

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

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

Always enforce the 2GB filesize limit on 32bit architectures.
Clean up a couple of messages


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

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

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

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

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

chew than necessary.


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

front of the linked list where they will be found faster later on.


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

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

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

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

I thought so previously.



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

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

Possibly ticket #164


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

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

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

legitimate error conditions.


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

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

Make HTC_Rx() return a distinct value for overflow/blast.
Teach vca_handover() to handle HTC_Rx() return status
Use HTC_Rx/vca_handover this way in all three acceptors.
Eliminate vca_pollsession()
Teach CNT_First() about HTC_Rx states.
Log which acceptor we use in shmlog



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

Drop leading whitespace if so informed.


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

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

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

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

we know what transactions trigger problems in that code.



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

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

actually paying attention to what goes on.


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

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

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

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

malloc'ing them.

This should reduce the N(nobj) swap-loading considerably.



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

Dump sizes of various structures on startup.



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

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

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

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

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

The intent is to be able to do things like:

	backend b1 {
		set backend.host = "fs.freebsd.dk";
		set backend.port = "82";
	}
	backend b2 {
		set backend.host = "fs.freebsd.dk";
		set backend.port = "81";
	}
	backend b3 {
		set backend.host = "fs.freebsd.dk";
		set backend.port = "80";
	}

	sub vcl_recv {
		remove req.http.cookie;
		if (req.restarts == 0) {
			set req.backend = b1;
		} else if (req.restarts == 1) {
			set req.backend = b2;
		} else {
			set req.backend = b3;
		}
	}

	sub vcl_fetch {
		if (obj.status != 200) {
			restart;
		}
	}




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

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