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

I need a printout for a code-walkthrough and this commit wraps lines,
removes trailing space, space before TAB and other iregularities.

Some generated files have been compacted a bit.

A few changes to comments along the way.



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

* Fri Oct 17 2008 Ingvar Hagelund <ingvar@linpro.no> - 2.0.1-1
- 2.0.1 released, a bugfix release. New upstream sources
- Package now also available in EPEL



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

on the worker thread stack, we cannot just let another thread pick
up.

This is not as much a fix as a workaround: simply sleep until the
object we wait for is no longer busy.

The issue may have to be revisited in the long run, but for 2.0.x
this will have to do.

Fixes #345



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

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

Fixes:	#354



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

Increased the stack size from 16K to 32K for the threads as it caused seg.fault. on Linux when writing formated to stderr (stdout worked).


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

- Readded the debugflag patch. It's so practical
- Added a strange workaround for make check on ppc64



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

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

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

Should be merged into 2.0


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

Thanks to cby for fixing this up and HTMLising it.


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

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

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

Write up changelog for 2.0


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

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

also, add pointer to doc/ directory.

Fixes: #353


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

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

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

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

Remove two spurious newlines in shmlog messages.
Assert that restarts is zero when we begin.



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

test work reliably on my machine.

Also set the reponse text to a recognizable text for improved logreading
should it fail again.



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

It seems like glibc's getaddrinfo is entirely happy to accept 70000 as
a valid port, so use something that's not a valid service name so make
check still works.


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

later.  Use EOF-encoding for sessions where the request is lower
HTTP protocol versions.



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

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

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

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

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

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

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

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

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

unexpected result codes.



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

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

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

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

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

IPv4 & IPv6 address in /etc/hosts' localhost entry.

Use "127.0.0.1" intead.

Send me a telegram when IPv6 matters.



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

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

tests a given number of times:

	varnishtest -n 100 tests/b*.vtc




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