[6.0] 73e498df7 Retire also the reference to VSM_NOPID in docs

Martin Blix Grydeland martin at varnish-software.com
Fri Oct 18 13:23:08 UTC 2019


commit 73e498df73280cba50a85dc3390c55845bbd8f04
Author: Martin Blix Grydeland <martin at varnish-software.com>
Date:   Wed Sep 11 13:04:13 2019 +0200

    Retire also the reference to VSM_NOPID in docs
    
    Ref previous commit to remove the use of kill(signull) on the pids of the
    Varnish processes to test liveness.

diff --git a/doc/sphinx/reference/vsm.rst b/doc/sphinx/reference/vsm.rst
index 7771b0110..d9a689c55 100644
--- a/doc/sphinx/reference/vsm.rst
+++ b/doc/sphinx/reference/vsm.rst
@@ -97,22 +97,3 @@ a chance to discover the deallocation.
 
 The include file <vapi/vsm.h> provides the supported API for accessing
 VSM files.
-
-VSM and Containers
-------------------
-
-The varnish way works great with single purpose containers. By sharing
-the varnish working directory read-only, vsm readers can be run in
-containers separate from those running varnishd instances on the same
-host.
-
-When running varnishd and vsm readers in the same process namespace,
-pid information can be used by vsm readers to determine if varnishd
-processes are alive.
-
-But, when running varnishd and vsm readers in different containers,
-the pid information has no relevance and may even be ambiguous across
-name spaces.
-
-Thus, with such setups, the environment variable VSM_NOPID needs to be
-set for vsm readers to disable use of pid information.


More information about the varnish-commit mailing list