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

properly close the connection when doing so.

Fixes 524



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

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

a table produced from the CLI parameter tables.

In the future all updates to these descriptions SHALL happen in the
CLI tables in the C source code.

Fixes	#419



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

which only does something if -DDIAGNOSTIC was configured.

First secret superpower is "-x dumpmdoc" which emits a -mdoc suitable
table of all run-time parameters, which can be absorbed into the
varnishd.1 manual page, so we do not have to maintain the text in
two different places.



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

Fixes #592



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

out.



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

storage space.

Fixes	590



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

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

sockets as fast as we can, so that a new copy of varnishd can get at them.

Fixes	#622



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

If the master pid is active when we start, we issue a message about
this, (with a hint about -n) and exit.

If the master pid is not active, but the child pid is, we issue a
message about it presumably being busy dying, dump the SHMFILE and
create a new one.  (This only saves our bacon, if the dying
process manages to close the listening sockets before we need them).

This should end any confusion that might arise from accidentally
running multiple varnishes at the same time.

Fixes #620



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

the worker thread.



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

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

simply be dying on us.  Instead return the designed error code for
this: CLIS_COMM 

Fixes	#639



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

object on the LRU list, we may not be holding the last reference.

Fixes:	#634

Tip of hat to:	Matt Page for execellent diagnosis & patch.



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

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