git-svn-id: http://www.varnish-cache.org/svn/tags/varnish-2.0@3307 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3306 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3305 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@3304 d4fa192b-c00b-0410-8231-f00ffab90ce4

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

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

Write up changelog for 2.0


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

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

also, add pointer to doc/ directory.

Fixes: #353


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

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

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

git-svn-id: http://www.varnish-cache.org/svn/trunk@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@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@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@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@3292 d4fa192b-c00b-0410-8231-f00ffab90ce4

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

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

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

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

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

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

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

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

unexpected result codes.



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

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

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

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

git-svn-id: http://www.varnish-cache.org/svn/trunk@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@3278 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk@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@3276 d4fa192b-c00b-0410-8231-f00ffab90ce4

Suggested by:	 "chen xiaoyong"



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

- Synced rpm changelog from fedora. There was some strange items that
  had to be sorted


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

* Wed Oct 08 2008 Ingvar Hagelund <ingvar@linpro.no> - 2.0-0.11.rc1
- 2.0-rc1 released. New upstream sources
- Added a patch for test a00008, from r3269
- Removed condrestart in postscript at upgrade. We don't want that.



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

(or might not) be the root cause of #346:

The delay function would access the toplevel log element from client/server
contexts with no logging.

Fix by passing the log element to the subcommands.

This race would only affect testcases using delay or sema inside client
or server threads.

Revert test a00008.vtc to use only one sema, using two just moved the
race condition.

This also has the side effect of moving "sema" related messages to
the tread that carries out the "sema" operation.

Various other cleanups now that I had my fingers in the code anyway:
memory leaks plugged, stylistic nits etc.



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

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

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

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

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