Tailored assertions for priv_addset and setppriv, assert that
setppriv(PRIV_OFF) succeeds when waiving privileges.

fixes varnish builds on any Solaris OS older than onnv_140 due to
too strict assertions from [c613b135570f87535839e3a94630880d16910f4f]

add history of solaris privileges

better comments

Submitted by:	Nils Goroll
Fix varnishncsa memory leaks on duplicate headers
Increase the 'client_workspace' for 32bit machines to be twice the
size of the 'http_req_size' so that we don't run out of WS in case
of client pipelining.

Fixes	#1185
Don't always check the sign after smp_append_sign().

Remove the XXXAZ(smp_chk_sign) after smp_append_sign(), as it causes
heavy unnecessary CPU usage after each sign update. No assertion
reports have come from this test, so there is no reason to expect the
signs not working.
Return false if req.backend.health is accessed in vcl_deliver{} where
this information is no longer available.

Fixes #1228
Count reloaded bans in VSC::bans_req

Replace some magic numbers by #defines and segregate the ban-string

Base patch from:	martin
Fixes #1225
Polish up cache_ban inspired by Martins 04/15 patch.

Add a function for comparing ban-strings, mostly to have a place to
put the explanatory comment.
Centralize GONE'ing of bans, and also mark their spec GONE,
including truncating the length.

Inspired by:  patches and talks from martin
No point in referencing ancient history
Use a red-black tree for storing the varnishtop entries

When using varnishtop -1 on a large log file, the old linked list
approach was very slow.  Using a tree increases performance
significantly.  In a test, old was 15 minutes, 52 seconds, new code
changes that to about 1.8 seconds.
Don't hide the last ban in the list on the CLI ban.list output

The ban.list output would hide the very last ban on the list unless
the lurker debug flag was set. This hides useful debugging information
(how many objects are stuck on the last ban), without giving any
apparent benefit. Remove the hide code.
Clarify which timeout was reached

When looking at varnishlog it looks like it is send_timeout that was reached,
but in fact it is idle_send_timeout. Clarify the language so the user
understands which parameter to adjust.
Minor cleanups in varnishtop

Some minor cleanups, no functional changes.  Thanks to Federico
Schwindt for pointing this out.
PATCH: fix some warnings during configure/compilation

Hi,

The diff below fixes one warning during configure and two during compilation on OpenBSD (and maybe elsewhere):

checking pthread_np.h usability... no
checking pthread_np.h presence... yes
configure: WARNING: pthread_np.h: present but cannot be compiled
configure: WARNING: pthread_np.h:     check for missing prerequisite headers?
configure: WARNING: pthread_np.h: see the Autoconf documentation
configure: WARNING: pthread_np.h:     section "Present But Cannot Be Compiled"
configure: WARNING: pthread_np.h: proceeding with the compiler's result
configure: WARNING:     ## -------------------------------------------- ##
configure: WARNING:     ## Report this to varnish-dev@varnish-cache.org ##
configure: WARNING:     ## -------------------------------------------- ##

varnishadm.c:190: warning: implicit declaration of function 'add_history'

cache/cache_main.c:82: warning: implicit declaration of function 'pthread_set_name_np'

Comments? OK?

f.-
Add vtree.h to _SOURCES
Only use readline/history.h if no edit/readline/redline.h

it seems edit/readline/readline.h and readline/history.h are
incompatible on FreeBSD, so only include one.  Hopefully this works on
OpenBSD still.
Reenable CLANG
White space fixes
Delay the accept task until all initialization has been completed.

This resolves the race where the pools might accept connections and
start processing them before a lot of the initialization routines has
finished.
Include config.h earlier, needed for Solaris