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
5679cc70
Commit
5679cc70
authored
Mar 10, 2017
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Summarize changes in varnishd command-line options in Upgrading to 5.1
parent
78419843
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
34 additions
and
1 deletion
+34
-1
varnishd.rst
doc/sphinx/reference/varnishd.rst
+1
-1
changes-5.1.rst
doc/sphinx/whats-new/changes-5.1.rst
+1
-0
upgrading-5.1.rst
doc/sphinx/whats-new/upgrading-5.1.rst
+32
-0
No files found.
doc/sphinx/reference/varnishd.rst
View file @
5679cc70
...
...
@@ -204,7 +204,7 @@ Advanced, development and debugging options
Print VCL code compiled to C language and exit. Specify the VCL file
to compile with the -f option. Either -f or -b must be used with -C,
and -C cannot be used with -F.
and -C cannot be used with -F
or -d
.
-V
...
...
doc/sphinx/whats-new/changes-5.1.rst
View file @
5679cc70
...
...
@@ -25,6 +25,7 @@ years we have been around now.
Guys, "Thanks" doesn't even start to cover it and we wish you all
the best for the future!
.. _whatsnew_clifile:
Startup CLI command file
~~~~~~~~~~~~~~~~~~~~~~~~
...
...
doc/sphinx/whats-new/upgrading-5.1.rst
View file @
5679cc70
...
...
@@ -7,6 +7,38 @@ Upgrading to Varnish 5.1
varnishd command-line options
=============================
If you have to change anything at all for version 5.1, then most
likely the command-line options for `varnishd` in your start scripts,
because we have tightened restrictions on which options may be used
together. This has served mainly to clarify the use of options for
testing purposes, for example using ``varnishd -C`` to check a VCL
source for syntactic correctness. We have also added some new options.
The details are given in :ref:`varnishd(1)`, but here's a summary:
* Added ``-I clifile`` to run CLI commands at startup, before the
worker process starts. See :ref:`whatsnew_clifile`.
* More than one ``-f`` option is now permitted, to pre-load VCL
instances at startup. The last of these becomes the "boot" instance
that is is active at startup.
* Either ``-b`` or one or more ``-f`` options must be specified, but
not both, and they cannot both be left out, unless ``-d`` is used to
start `varnishd` in debugging mode. If the empty string is specified
as the sole ``-f`` option, then `varnishd` starts without starting
the worker process, and the management process will accept CLI
commands.
* Added ``-?`` to print the usage message, which is only printed for
this option.
* Added the ``-x`` option to print certain kinds of documentation and
exit. When ``-x`` is used, it must be the only option.
* Only one of ``-F`` or ``-d`` may be used, and neither of these can
be used with ``-C``.
* Added the ``workuser`` parameter to the ``-j`` option.
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