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
2eb85e13
Commit
2eb85e13
authored
Nov 04, 2014
by
Federico G. Schwindt
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
More changes from varnish 3 and some specific to master
parent
b4391c05
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
9 deletions
+10
-9
upgrading.rst
doc/sphinx/whats-new/upgrading.rst
+10
-9
No files found.
doc/sphinx/whats-new/upgrading.rst
View file @
2eb85e13
...
@@ -145,14 +145,7 @@ The `purge;` keyword has been retired.
...
@@ -145,14 +145,7 @@ The `purge;` keyword has been retired.
obj is now read-only
obj is now read-only
~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~
`obj` is now read-only. `obj.hits`, if enabled in VCL, now counts per
`obj` is now read-only. `obj.last_use` has been retired.
objecthead, not per object. `obj.last_use` has been retired.
Note that obj.hits may not be reset in some cases where bans are in use. See
bug 1492_ for details.
.. _1492: https://www.varnish-cache.org/trac/ticket/1492
Some return values have been replaced
Some return values have been replaced
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...
@@ -218,6 +211,14 @@ If you are using a lot of VMODs, you may need to increase
...
@@ -218,6 +211,14 @@ If you are using a lot of VMODs, you may need to increase
either `workspace_backend` and `workspace_client` based on where
either `workspace_backend` and `workspace_client` based on where
your VMOD is doing its work.
your VMOD is doing its work.
thread_pool_purge_delay
~~~~~~~~~~~~~~~~~~~~~~~
`thread_pool_purge_delay` has been renamed to `thread_pool_destroy_delay`
and it is in seconds now (previously was milliseconds).
thread_pool_add_delay and thread_pool_fail_delay
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
They are in seconds now (previously were milliseconds).
New parameters since 3.0
New parameters since 3.0
========================
========================
...
...
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