Fix copy&paste mistake in test b00006



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

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

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

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

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

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

Fixes ticket 263



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

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

before the herder starts, in order that it will create the minimum
number of threads in the pool.


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

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

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

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

read-ahead, NUL the rxbuffer.



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

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

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

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

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

correctly spotted: deconsting through strchr().

A couple of other flexelint nits while here




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

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

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

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

Here is the fix for the regsub() issue: Don't release negative bytecounts,
we have the special variant WS_ReleaseP() just for jobs like this.



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

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

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

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

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

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

the storage file by accident.



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

address works.


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

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

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

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

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

and one IPv6, resort to "127.0.0.1"



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

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

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

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

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

varnish debugging output a separate log handle.

(The point here is to maximize the amount of concurrency we can
simulate.  Down the road, the logging may become pre thread with
a final sorting pass to get all the messages correctly interleaved.)



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

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