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

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

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

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

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

(It should be readily possible to access the shmlog using just libvarnishapi,
but for some of or more advanced support programs, we will use the smart
stuff in libvarnish to improve code quality)



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

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

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

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

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

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

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

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

complexity.

Do a -n collision check, and create a new file always.



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

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

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

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

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

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

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

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

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

If the remote end RST's a TCP connection, all socket related syscalls
seems to return EINVAL.



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

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

end of the object, but I did.

Fixes #704.

Reported by:	Luc Saillard


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

Submitted by: 	Luc Saillard


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

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

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

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

the tree is sane at all points.



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

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

using the objhead as carrier for it.

The time difference between objhead freeing and Y freeing is very
significant on systems with rolling URLS (ie: "article=%d") resulting
in far too many objheads being stuck on the cooling list.



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

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

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

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

with -smalloc stats:

Split SMA relevant fields into their own MAC_STAT_SMA macros, and make it
possible to include stat_field.h without all MAC_STAT* macrods defined.

Move SMA relevant fields from struct varnish_stats to their own 
varnish_stats_sma.

Teach varnishstat to enumerate fields from a varnish_stats_sma.  (This
code looks like it should/could be much more general, and probably
libvarnisapi candidate).  For now only curses mode updated.

In storage_malloc.c, allocate a shm_alloc for a struct varnish_stats_sma
for each instance (in ->ready(), because we have no shm during arg
processing in ->init(), update the counters therein.




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

over that list, rather than enumerate all stats for each iteration.



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

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

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

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