Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
libvmod-blobdigest
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
2
Issues
2
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
uplex-varnish
libvmod-blobdigest
Commits
2654795d
Commit
2654795d
authored
Nov 04, 2016
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
clarify LIMITATIONS in the doc concerning memory allocation
parent
7ea7a4b7
Pipeline
#65
skipped
Changes
2
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
10 additions
and
2 deletions
+10
-2
README.rst
README.rst
+5
-1
vmod_blobdigest.vcc
src/vmod_blobdigest.vcc
+5
-1
No files found.
README.rst
View file @
2654795d
...
...
@@ -487,12 +487,16 @@ check``, the VMODs ``blobcode`` and ``blob`` must be installed (see
LIMITATIONS
===========
The VMOD allocates memory for BLOBs in Varnish workspace. If its
For operations outside of ``vcl_init``, the VMOD allocates memory for
BLOBs and other internal structures in Varnish workspace. If its
methods or functions fail, as indicated by "out of space" messages in
the Varnish log (with the ``VCL_Error`` tag), then you will need to
increase the varnishd parameters ``workspace_client`` and/or
``workspace_backend``.
For operations invoked in ``vcl_init``, the VMOD allocates heap
memory, and hence is only limited by available RAM.
INSTALLATION
============
...
...
src/vmod_blobdigest.vcc
View file @
2654795d
...
...
@@ -426,12 +426,16 @@ check``, the VMODs ``blobcode`` and ``blob`` must be installed (see
LIMITATIONS
===========
The VMOD allocates memory for BLOBs in Varnish workspace. If its
For operations outside of ``vcl_init``, the VMOD allocates memory for
BLOBs and other internal structures in Varnish workspace. If its
methods or functions fail, as indicated by "out of space" messages in
the Varnish log (with the ``VCL_Error`` tag), then you will need to
increase the varnishd parameters ``workspace_client`` and/or
``workspace_backend``.
For operations invoked in ``vcl_init``, the VMOD allocates heap
memory, and hence is only limited by available RAM.
INSTALLATION
============
...
...
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