[master] 570a92b Update docs about UDS with varnishtest/vtc in "Upgrading to 6.0".

Geoff Simmons geoff at uplex.de
Mon Mar 12 17:14:08 UTC 2018

commit 570a92be487598747aec1bdb0c451afc6ba56af0
Author: Geoff Simmons <geoff at uplex.de>
Date:   Mon Mar 12 18:12:52 2018 +0100

    Update docs about UDS with varnishtest/vtc in "Upgrading to 6.0".

diff --git a/doc/sphinx/whats-new/upgrading-6.0.rst b/doc/sphinx/whats-new/upgrading-6.0.rst
index 4d835e8..f93b8d2 100644
--- a/doc/sphinx/whats-new/upgrading-6.0.rst
+++ b/doc/sphinx/whats-new/upgrading-6.0.rst
@@ -429,7 +429,7 @@ Other changes
     with the backend name field -- the second field in
-* ``varnishtest(1)``:
+* ``varnishtest(1)`` and ``vtc(7)``:
   * The ``client -connect`` and ``server -listen`` commands in vtc
     scripts now allow Unix domain sockets as addresses, recognized
@@ -450,12 +450,19 @@ Other changes
     ``varnish -arg`` command with the appropriate settings for the
     ``-a`` command line argument, see :ref:`varnishd(1)`.
+    The ``varnish -vcl+backend`` command now works to include backend
+    definitions for server objects that are listening at UDS. Backend
+    declarations are implicitly included for such servers with the
+    appropriate ``.path`` setting.
     A convenient location for socket files to be used in a test is the
     temporary directory created by ``varnishtest`` for each test,
     whose path is held in the macro ``${tmpdir}``. So this is a common
     idiom for tests that involve UDSen::
-      varnish v1 -arg "-a ${tmpdir}/v1.sock" -vcl { ... } -start
+      server s1 -listen "${tmpdir}/s1.sock" { ... } -start
+      varnish v1 -arg "-a ${tmpdir}/v1.sock" -vcl+backend { ... } -start
       client c1 -connect "${tmpdir}/v1.sock" { ... } -run

More information about the varnish-commit mailing list