Gitweb:
http://git.exim.org/exim.git/commitdiff/8121f0285d4ce30921cf4924d615a143bfdfb956
Commit: 8121f0285d4ce30921cf4924d615a143bfdfb956
Parent: 8f1cff481ae440b8ced8601cd2a2134714580d3c
Author: Phil Pennock <pdp@???>
AuthorDate: Sun Jan 30 03:34:31 2011 -0500
Committer: Phil Pennock <pdp@???>
CommitDate: Sun Jan 30 03:34:31 2011 -0500
sudo !tty_tickets; correct config file list.
sudo needs to permit sudo w/o a TTY.
The config file used is the same for each test, the individual config
files are made available under a particular name. Correct that advice.
---
test/README | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/test/README b/test/README
index 2a1a79c..bdd840a 100644
--- a/test/README
+++ b/test/README
@@ -69,6 +69,12 @@ In order to run this test suite, the following requirements must be met:
tracks the two users independently. Using the same user would result
in false positives on some tests.
+ Further, some tests invoke sudo in an environment where there might not be
+ a TTY, so tickets should be global, not per-TTY. Taking this all together
+ and assuming a user of "exim-build", you might have this in sudoers:
+
+ Defaults:exim-build timestamp_timeout=480,!tty_tickets
+
(3) The login under which you run the tests must be in the exim group so that
it has access to logs, spool files, etc. The login should not be one of the
names "userx", "usery", "userz", or a few other simple ones such as "abcd"
@@ -140,7 +146,7 @@ RUNNING THE TEST SUITE
(3) Run "./configure" and then "make". This builds a few auxiliary programs
that are written in C.
-(4) ls -1 $PWD/confs/* >> your_TRUSTED_CONFIG_LIST_filename
+(4) echo $PWD/test-config >> your_TRUSTED_CONFIG_LIST_filename
(5) Run "./runtest" (a Perl script) as described below.
