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

DocBook, and that I don't have <filename>, <literal>, <varname> etc. -
just <code>.


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

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

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

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

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

Move the VRT initializer for simple backends home.

Add a backend method to get hostname.  This may be a hack.

Move fields private to "simple" to its private structure.

Add cleanup method to backend, so we can collect the garbage.



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

when a new VCL instantiates a backend.

Drop backends when their reference count goes to zero.



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

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

For now all we have is a "simple" method, but we want more complex
methods later on, round-robin, least-busy and so on.

For now, fall into the other ditch and move everything to 
cache_backend_simple.c, we will move bits back as the gain generality.



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

a couple of now pointless debugging messages in pipe mode.


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

across unchanged, otherwise the semantics of the Connection: header cannot
be interpreted correctly by the server.

wget(1) could trigger this problem and would have to wait for the server
to close the (seemingly idle) connection before continuing.



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

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

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

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

It's a fine point of C-linguistics, but I have to admit that in
certain universes it would have a point.  Not this one though.




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

code that invokes it.

If fmtcheck(3) is available, we refuse pedal target practice.



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

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

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

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

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

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

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

A svn trunk build needs automake, autoconf and libtool to build. A release tarball can remove these requirements.

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

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

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

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

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

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

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

Don't nuke t_end timestamp, we need it for StatSess logentry.



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

Otherwise we will for ever be repeating the same command over and over,
no matter what the input to the cli might be.


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

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

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

going on.  Also take care of a bug where strchr() was used on a non-NUL-
terminated buffer.  This fixes #134.


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

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

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

- Update for 1.1 branch
- Added the devel package for the header files and static library files
- Added a varnish user, and fixed the init script accordingly



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

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

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