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

Always wrap the log on worker process startup.

Detect such wraps in libvarnishapi



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

Handle shmlog in 32bit byte aligned words, that saves wear and tear
on cpu write combining and makes things a bit faster.



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

with inline assembler.

I cannot possibly express the magnitude of this particular POSIX FAIL!


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

applicable and can be implemented more efficiently this way.

The new syntax is an expansion of the old, which allows
"class.ident.name" or just "name" patterns to be specified.

A pattern which starts with '^' excludes the matching fields,
otherwise the pattern includes them.

If the first pattern is an exclude pattern, all fields start
out included, and vice versa.

Notice that "class" and "ident" fields always must have their
trailing '.' even if they are empty.

Each subcomponent can have a '*' suffix, which will ("glob") match
anything.

Multiple "-f" arguments can be given, they will be concatenated.

All patterns will be tested sequentially, and the last one that
matches determines the result.

Example:

	-f "SMA..sma_nreq,^SMA.ba*." -f "shm_*"

This will return:
	SMA.storage_0.sma_nreq
	shm_records
	shm_writes
	...

but not:
	SMA.storage_0.sma_nobj
	SMA.bar.sma_nreq
	sms_nreq
	...




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

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

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

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

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

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

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

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

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

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

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

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

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

is faster, more handy and easier to extend in the future.



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

restarted.



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

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

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

Rewrite -1 and -x handing to use new VSL_IterStat() support.



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

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

dynamically allocated such.



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

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

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