From: des Date: Tue, 18 Dec 2007 17:00:19 +0000 (+0000) Subject: Full change log for 1.1.2 (corresponding to branches/1.1 as of today). X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2ecfd0655099cbe4af4fddb533d5751e0935141f;p=varnish Full change log for 1.1.2 (corresponding to branches/1.1 as of today). References to tickets have been included where I have been able to track down the ticket corresponding to a particular commit. git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@2300 d4fa192b-c00b-0410-8231-f00ffab90ce4 --- diff --git a/varnish-cache/doc/changes-1.1.1-1.1.2.xml b/varnish-cache/doc/changes-1.1.1-1.1.2.xml index 76e10f51..fc19f70a 100644 --- a/varnish-cache/doc/changes-1.1.1-1.1.2.xml +++ b/varnish-cache/doc/changes-1.1.1-1.1.2.xml @@ -37,17 +37,113 @@ A bug in the VCL compiler which would cause a double-free - when processing include directives has been + when processing include directives has been fixed. - + A resource leak in the worker thread management code has + been fixed. + + + + When connecting to a backend, Varnish will usually get the + address from a cache. When the cache is refreshed, existing + connections may end up with a reference to an address structure + which no longer exists, resulting in a crash. This race + condition has been somewhat mitigated, but not entirely + eliminated (see .) + + + + Varnish will now pass the correct protocol version in pipe + mode: the backend will get what the client sent, and vice + versa. + + + + The core of the pipe mode code has been rewritten to + increase robustness and eliminate spurious error messages when + either end closes the connection in a manner Varnish did not + anticipate. + + + + A memory leak in the backend code has been plugged. + + + + When using the kqueue acceptor, if a client + shuts down the request side of the connection (as many clients + do after sending their final request), it was possible for the + acceptor code to receive the EOF event and recycle + the session while the last request was still being serviced, + resulting in a assertion failure and a crash when the worker + thread later tried to delete the session. This should no longer + happen (see .) + + + + A mismatch between the recorded length of a cached object + and the amount of data actually present in cache for that object + can occasionally occur (see .) This has been + partially fixed, but may still occur for error pages generated + by Varnish when a problem arises while retrieving an object from + the backend. + + + + + varnishhist + + + Pressing 0 though 9 while + varnishhist is running will change the refresh + interval to the corresponding power of two, in seconds. + + + + + varnishncsa + + + The varnishncsa tool can now daemonize and + write a PID file like varnishlog, using the same + command-line options. It will also reopen its output upon receipt + of a SIGHUP if invoked with -w. + + + + + varnishstat + + + Pressing 0 though 9 while + varnishstat is running will change the refresh + interval to the corresponding power of two, in seconds. Build system + + Varnish's <queue.h> has been modified + to avoid conflicts with <sys/queue.h> on + platforms where the latter is included indirectly through system + headers. + + + + Several steps have been taken towards Solaris + support, but this is not yet complete. + + + + When configure was run without an explicit + prefix, Varnish's idea of the default state directory would be + garbage and a state directory would have to be specified + manually with -n. This has been corrected. +