Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
f9822994
Commit
f9822994
authored
Mar 12, 2018
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document UDS backends in "Upgrading to 6.0".
parent
6ac01261
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
32 additions
and
0 deletions
+32
-0
upgrading-6.0.rst
doc/sphinx/whats-new/upgrading-6.0.rst
+32
-0
No files found.
doc/sphinx/whats-new/upgrading-6.0.rst
View file @
f9822994
...
@@ -52,6 +52,38 @@ that must be done outside of the Varnish configuration).
...
@@ -52,6 +52,38 @@ that must be done outside of the Varnish configuration).
If you continue using only IP addresses in your ``-a`` arguments, you
If you continue using only IP addresses in your ``-a`` arguments, you
won't have to change them.
won't have to change them.
Unix domain sockets as backend addresses
========================================
A backend declaration may now have the ``.path`` field to specify a
Unix domain socket to which Varnish connects::
backend my_uds_backend {
.path = "/path/to/backend.sock";
}
One of the fields ``.host`` or ``.path`` must be specified for a
backend (but not both).
The value of ``.path`` must be an absolute path (beginning with
``/``), and the file at that path must exist and be accessible to
Varnish at VCL load time; and it must be a socket.
The platform-specific restrictions on UDSen mentioned above apply of
course to backends as well; but in this case your deployment of the
peer component listening at the socket file must fulfill those
conditions, otherwise Varnish may not be able to connect to the
backend.
The path of a socket file may also be specified in the
``varnishd -b`` command-line option (see varnishd
:ref:`ref-varnishd-options`)::
$ varnishd -b /path/to/backend.sock
The value of ``-b`` must fulfill the same conditions as the ``.path``
field in a backend declaration.
varnishd parameters
varnishd parameters
===================
===================
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment