From c1ed13d8ff8670bf80ec8609dace45f0cf113614 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Thu, 31 May 2007 06:44:18 +0000 Subject: [PATCH] Update README git-svn-id: https://bacula.svn.sourceforge.net/svnroot/bacula/trunk@4946 91ce42f0-d328-0410-95d8-f526ca767f89 --- regress/README | 27 +++++++++++++++++++++++---- 1 file changed, 23 insertions(+), 4 deletions(-) diff --git a/regress/README b/regress/README index 040f87fc11..efd85e9e8e 100644 --- a/regress/README +++ b/regress/README @@ -115,10 +115,29 @@ conf files, and you do not need a new copy of the source, you can simply do: make sed Debugging failed tests: -The simplest thing to do is to edit tests/xxxx where xxxx is the name of -the test, and change the line "set_debug 0" to "set_debug 1". If the test has -not been updated to have the debug variable, please notify Kern, and I -will be happy to fix it -- I am upgrading them one at a time. +Prior versions required editing the tests/xxxx and changing a debug flag. +However, that has been replaced by two environment variables: + + REGRESS_DEBUG + REGRESS_WAIT + +If you define REGRESS_DEBUG, e.g. + + REGRESS_DEBUG=1 + export REGRESS_DEBUG + +then run a test, it will display the job and debug output. + +If you define REGRESS_WAIT, the script will stop and request: + +Start Bacula under debugger and enter anything when ready ... + +At this point, you can start any of the daemons under the debugger, +then answer the message by entering any character. The script will +then continue. For any daemon or daemons that you have manually started, +you will see an error message when the script attempts to run a second +copy, but those messages can be ignored. This makes it reasonably easy +to run any component or components under the debugger if necessary. Also, if you run from time to time on a computer that is not connected to the network, please be sure that "hostname" is set to "localhost", -- 2.39.5