summaryrefslogtreecommitdiff
path: root/regress
diff options
context:
space:
mode:
authorDarren Tucker <dtucker@zip.com.au>2005-03-14 23:02:46 +1100
committerDarren Tucker <dtucker@zip.com.au>2005-03-14 23:02:46 +1100
commitf899e6a5265ac173acbac51022a2512643ec909c (patch)
tree2e14d3e0075ae40efb97d71e100f8c453d607a35 /regress
parent1d55ca748d6f1cab42aba290a0b77bd142830401 (diff)
20050312
- (dtucker) [regress/test-exec.sh] DEBUG can cause problems where debug output ends up in the client's output, causing regress failures. Found by Corinna Vinschen. (got 4.0 branch and HEAD slightly askew, this is to resync)
Diffstat (limited to 'regress')
-rw-r--r--regress/test-exec.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/regress/test-exec.sh b/regress/test-exec.sh
index 4e53449be..bd0c025ba 100644
--- a/regress/test-exec.sh
+++ b/regress/test-exec.sh
@@ -197,7 +197,7 @@ cat << EOF > $OBJ/sshd_config
197 #ListenAddress ::1 197 #ListenAddress ::1
198 PidFile $PIDFILE 198 PidFile $PIDFILE
199 AuthorizedKeysFile $OBJ/authorized_keys_%u 199 AuthorizedKeysFile $OBJ/authorized_keys_%u
200 LogLevel DEBUG 200 LogLevel VERBOSE
201 AcceptEnv _XXX_TEST_* 201 AcceptEnv _XXX_TEST_*
202 AcceptEnv _XXX_TEST 202 AcceptEnv _XXX_TEST
203 Subsystem sftp $SFTPSERVER 203 Subsystem sftp $SFTPSERVER