[4.0] a382e0d Change exit code documentation so highest is most severe. Dont mention exit(4)

Lasse Karstensen lkarsten at varnish-software.com
Mon Sep 22 16:38:24 CEST 2014


commit a382e0d02785d71f2fa5c2d47f21ce5e0d6ba7c0
Author: Nils Goroll <nils.goroll at uplex.de>
Date:   Wed Aug 27 22:02:59 2014 +0200

    Change exit code documentation so highest is most severe. Dont mention exit(4)
    
    After discussion with phk: exit(4) is a real exception, we should abort() whenever
    possible.
    
    The error codes patch is still to be committed.

diff --git a/doc/sphinx/reference/varnishd.rst b/doc/sphinx/reference/varnishd.rst
index 3375f3f..6014637 100644
--- a/doc/sphinx/reference/varnishd.rst
+++ b/doc/sphinx/reference/varnishd.rst
@@ -256,15 +256,9 @@ Varnish and bundled tools will, in most cases, exit with one of the
 following codes
 
 * `0` OK
-* `1` Configuration / parameter error
-* `2` Some other error which could be system-dependend and/or transient
-
-In addition to these, the `varnishd` child process will exit with
-status code `4`
-
-* in a panic situation when coredumps are disabled and
-* in panic-like situations when triggering an actual panic is not
-  possible.
+* `1` Some error which could be system-dependend and/or transient
+* `2` Serious configuration / parameter error - retrying with the same
+  configuration / parameters is most likely useless
 
 The `varnishd` master process may also OR its exit code
 



More information about the varnish-commit mailing list