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.

diff --git a/test/README b/test/README
index 2a1a79cc62b7fef9cd3bd6d2917601717797cf5e..bdd840a661e4f857b88a50817018ddbf796f6e74 100644 (file)
--- 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.
 
     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"
 (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.
 
 (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.
 
 
 (5) Run "./runtest" (a Perl script) as described below.