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

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

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

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

which has the opposite meaning (IMHO, the continuous display is the most
useful)

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

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

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

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

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

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

implemented).
Fix the usage string.

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

Fix the usage string.

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

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

of available storage on 32-bit Linux (most fields in struct statfs are long
instead of int64_t as in BSD)

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

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

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

run-time parameters.

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

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

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

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

Clean up the paramter stuff even more.



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

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

Give the managers main a struct cli and use that to call into
the paramter stuff for setting listen address.  More params to follow.

When setting the listen address, check that getaddrinfo() doesn't
hate it.



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

Make the listen address a parameter.



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

that way and we may eventually want a config file for varnishd to
control obscure parameters.



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

VCL tracing is responsible for a very large fraction of the shmlog
records and will generally only be used for debugging of VCL code.



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

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

large in general (think RTT) for this to make sense, it costs a syscall
and if a delay is used, at least two context switches.

We still capture sessions that do pipe-line avoiding the context switch
in that case, without incurring the syscall overhead.


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

knowing this at the end of a request.

Instead put the address + port in the ReqStart shmtag where it does
a lot of good.


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

It is not clear if this is a benefit or not.  There seems to be a significant
(100msec ?) inter-request gap and seeting the grace period that long
means tying up worker threads doing basically nothing.

Setting a short timeout (10msec) results in an extra system call which
practically never does anything good.

Unless benefit is shown, this stuff should be removed again.


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

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

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

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

need to use REG_STARTEND any more.


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

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

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

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

Also skip IP# from SessionReuse records.


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

 - use the correct headers
 - don't duplicate WRK_Flush()
 - pass the offset correctly

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

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