Eventually we need to separate the "max http header size" from the
workspace size, but that will take a bit of pondering.


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

requests, otherwise we end up filling it up with Content-Length: headers
if we manage to keep the backend busy.

Also make the snapshot of the preferred workspace-size volatile to ensure
that we are consistent.



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

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

path, or a path relative to $localstatedir/varnish.  By default, it is set
to the host name, which results in $localstatedir/varnish/$hostname.

This logic is centralized in instance.c, which is compiled into both
varnishd and libvarnishapi, with prototypes in varnishapi.h and heritage.h.


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

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

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

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

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

accordingly.



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

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

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

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

 
We need to process -P and -f arguments before we change directory.
(ticket 120)

(XXX: what about storage and hash arguments ??)

The daemon(3) call should not change our directory subsequently.
(ticket 121)
 
There is no need to enforce a hostname style format on the argument,
a directory nam makes much more sense, since that is what we need. 
Defaulting to /tmp instead of our hostname makes more sense (ticket 119).

This also allows the admin to use a different directory if /tmp is
mounted noexec (ticket 111) 
 
Put the directoryname used in the proctitle (via heritage)
 
XXX: for docs: vcl.load CLI commands will work relative to the -n directory.



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

is already open.  The filedescriptor will be closed.



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

up: implement a "sloppy" LRU list.  An object is placed on the list (or moved
to the head of the list if it's already on it and hasn't moved recently) by
calling LRU_Enter(), and removed by calling LRU_Remove().  LRU_DiscardSpace()
will iterate through the LRU list, starting at the back, and retire objects
(by adding them to the deathrow list) until the sum of the length of the
retired objects reaches a certain number.  Similarly, LRU_DiscardTime() will
retire objects which haven't moved since a specified cutoff date.  In both
cases, vcl_discard() will be given a chance to inspect the object and veto
its retirement.

Currently, LRU_Enter() and LRU_Remove() are called from HSH_Lookup() and
HSH_Deref() respectively.  There may be better alternatives.

Neither LRU_DiscardSpace() nor LRU_DiscardTime() is currently called from
anywhere.  There are a number of issues to consider: for instance, even if
LRU_DiscardSpace() is called when a high-water mark is reached, there is
still a possibility that the cache might fill up before it has had a chance
to finish and the hangman has had a chance to process the deathrow list.


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

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

are not on the expiry heap.


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

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

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

allocated and free space.


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

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

object is acceptable to all clients.


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

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

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

Visible from vcl_fetch() only.



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

This can happen if you get an IPv6 address for the -a argument, but
runs without IPv6 enabled in your kernel.  Typically happens only
for localhost.



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

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

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

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

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

Remove bogus "has_string" variable marking, it can be derived from the type.

Make obj.* variables valid in vcl_timeout() and vcl_discard()



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

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

their scope.  One example of this is the "req.hash" variable which only
exists in the vcl_hash method.



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

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

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

when -C is specified, this makes it easier to do completeness test on the
VRT interface.


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

This is for DES' work on LRU list.



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

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

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

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