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

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

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

compile time constant on all systems.

Pick it up with sysconf() instead.



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

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

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

these functions.

The [v]asprintf() functions are convenient shorthand, but suffer from
a number of problems, portability, cornercases and performance being
the most relevant to Varnish. 

Static buffers on the stack (see [v]bprintf macros, or sbufs (vsb)
are always better choices for us.



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

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

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

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

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

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

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

new sessions as such.  If we get no request in the session_linger
window, we punt the session over to the waiter, in order to not
tie up a worker thread longer than necessary.

This makes the session_linger a more important paramter to tune/get
right, but should also reduce our vulnerability to certain DoS attacks.



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

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

to the client absconding the TCP connection.

This comes to the fore on Solaris, where not only systemcalls which
push data through sockets (read,write,select...) return these errors,
but also socket-state calls (setsockopt, ioctl, fcntl) do.

Root cause of trouble in #626 & al.



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

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

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