Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
libvmod-esicookies
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
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-esicookies
Commits
58c407c0
Commit
58c407c0
authored
Oct 16, 2014
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
document --without-jemalloc to avoid the bundled jemalloc bug
parent
72dad508
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
5 deletions
+11
-5
README.rst
README.rst
+11
-5
No files found.
README.rst
View file @
58c407c0
...
@@ -208,11 +208,17 @@ KNOWN ISSUES
...
@@ -208,11 +208,17 @@ KNOWN ISSUES
* On Linux, if ``make check`` fails for `vmod_esicookies_reload.vtc`,
* On Linux, if ``make check`` fails for `vmod_esicookies_reload.vtc`,
inspect the error log. If it reports a segmentation violation
inspect the error log. If it reports a segmentation violation
(SIGSEGV) in varnishd, your varnish sources have most likely been
(SIGSEGV) in varnishd, your varnish sources have most likely been
compiled with the bundled jemalloc. Please make sure that an
compiled with the (outdated) bundled jemalloc.
up-to-date `jemalloc` development package is installed on your
system (probably called `libjemalloc-dev` or `jemalloc-devel`) and
To avoid this issue, either
re-build Varnish. Check the `config.log` for a `No system jemalloc
found` warning and re-iterate if this warning is found.
1. compile varnish ``--without-jemalloc``
2. or make sure that an up-to-date `jemalloc` development package is
installed on your system (probably called `libjemalloc-dev` or
`jemalloc-devel`) and re-build Varnish. Check the `config.log`
for a `No system jemalloc found` warning and re-iterate if this
warning is found.
* Varnish 3 releases differ in their behaviour with regard to empty
* Varnish 3 releases differ in their behaviour with regard to empty
headers. Setting a header to the result of the to_http0_e_ and
headers. Setting a header to the result of the to_http0_e_ and
...
...
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