critbit cooling-list, making this check invalid.

Spotted by:	Justin Pasher



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

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

picking up the object body.

Fixes #667



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

backend connection are chronological in the shmlog.



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

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

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

Fixes #655



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

syntax change



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

tfheen:  Please review



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

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

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

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

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

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

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

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

"single -d" mode, which nobody ever used, and make -d do what you expect
it to from all other daemons.

It was a nice idea though.



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

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

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

trigger atexit(3) processing.

Fixes #632



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

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

and bugs right now.




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

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

Found by:	luc/tom28



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

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

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

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

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

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

With level-triggered epoll, this should take care of the cpu-spinning that
we saw in #644, but needs to be confirmed.


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

but does handle the -S authentication for you.

You can now get a secure remote CLI connection by:

	ssh foohost varnisadm -T :8081 -S/etc/varnish_secret

Or you can:

	echo "help" | ssh foohost varnisadm -T :8081 -S/etc/varnish_secret



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

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

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

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

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

the #define is correct.



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

from the CLI.

Put in a separate source file, as it should be included in libvarnishapi
as well.



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

Use VSS_open() instead of home-rolling.



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

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

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