Update backend stats fields


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

There is no sane way to get sscanf to tell you how many characters 
were consumed, if you want to allow a variable number of arguments.
 
The special format %n is patently useless for this, because you 
have to insert it at every conceiveable point in the string and
that presumes full explicit whitespace markup.
 
Parse -w argument "by hand", to catch illegal input like "1,INF,15"
 
Tripped over by:        Stein Ove Rosseland <steinove@vg.no>
 
Fixes:  ticket #82



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

Rename the fields to make more sense



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

so we have to add our own stuff for that.

Without some kind of TTL, we would hit the DNS server once per failed
attempt to connect to the backend.

If the backend were down, we could hit it a LOT.

In the VCL code:

	backend foobar {
		[...]
		set backend.dnsttl = 20s;
	}

will assign a TTL for DNS lookups of this backends hostname+port
combination, we will not hit the DNS server more often that this.

The default is set at 30 seconds, short enough to make things are
workable in a load-balancing-via-DNS setups, yet long enough to not
pound the DNS server flat in case of backend failures.

NOTE that as long as we succeed in connecting to the backend we
do not perform new DNS lookups.  That will have to be revisited
along with possible load-balancing schemes for the backend(s).



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

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

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

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

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

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

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

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

Pointy hat to:	{ade,portsmgr}@freebsd.org


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

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

FreeBSD also.


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

Starting with 3.1, NetBSD uses statvfs and not statfs.

Submitted by:	Juan RP <juan@xtrarom.org>


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

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

the user asks; bail if max < min; fix usage string.

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

Make the pipe-juggling code slightly more readable.

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

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

remove the so-called advertising clause from these files' license,
making it compatible with the Debian Free Software Guidelines.  As
these files were obtained from FreeBSD, this change was discussed
with and approved by the FreeBSD core team.

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

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

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

Added wording regarding the origination of the source of
varnish with relation to debian.


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

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

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

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

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

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

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

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

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

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

gcc >= 3.3.
Now compiles on pristine etch-systems


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

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

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

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

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

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

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

WARNING: varnish will build and run, but the lack of a monotonic clock
may lead to strange behaviour if the clock is stepped (rather than skewed)
while varnish is running.

Thanks to Niklas Saers for providing a test environment.

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