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

and working, and panic with a somewhat usable message if not.

PS: And boy, are you screwed if my test sneaks though a kernel bug...



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

the features listed on the present platform



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

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

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

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

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

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

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

Don't update the pollfd state from the pipe, until we have dealt with
all sessions.

Strongly assert the pollfd state everywhere.



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

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

spurious test-failures if peoples DNS servers lie to them.

Fixes #356



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

now.



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

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

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

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

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

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

Fixes #644


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

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

Mention this in man page.

Update param list in man page.



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

When we do a lookup, we first try without the lock, if this gives
us a refcnt==0 objhead, we try again, with the lock.

When we deref an objhead, we would decrement the refcnt, holding oh->mtx,
then lock the critbit-lock and remove it from the tree.

It might be possible for a locked lookup to find an oh we just decremented
the refcnt off, and we did not check for refcnt==0 in that case.

Fix this, by removing the oh from the tree, holding the critbit-lock,
before decrementing the refcnt.  This way, a locked lookup can never
find a refcnt==0 oh in the tree, and the unlocked lookup still catches
this with the refcnt==0 check.




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

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

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

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

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

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

"Connection: close" or if a HTTP/1.0 backend does not send "Connection: keep-alive".

Fixes	#495



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

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

given.



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

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

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

of workspace, but the message will make more sense...



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

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

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

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

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

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

Fixes	#640



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

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