From 433f6c0f99d67bde2d3387ef4e6c25864732e14f Mon Sep 17 00:00:00 2001
From: dtucker <dtucker>
Date: Mon, 14 Mar 2005 12:02:46 +0000
Subject: [PATCH 1/1] 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)
---
 ChangeLog            | 5 +++++
 regress/test-exec.sh | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index 3c3edbdf..22eb47d8 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -10,6 +10,11 @@
    localized name of the local administrators group more reliable.  From
    vinschen at redhat.com.
 
+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.
+
 20050309
  - (dtucker) [regress/test-exec.sh] Set BIN_SH=xpg4 on OSF1/Digital Unix/Tru64
    so that regress tests behave.  From Chris Adams.
diff --git a/regress/test-exec.sh b/regress/test-exec.sh
index 4e53449b..bd0c025b 100644
--- a/regress/test-exec.sh
+++ b/regress/test-exec.sh
@@ -197,7 +197,7 @@ cat << EOF > $OBJ/sshd_config
 	#ListenAddress		::1
 	PidFile			$PIDFILE
 	AuthorizedKeysFile	$OBJ/authorized_keys_%u
-	LogLevel		DEBUG
+	LogLevel		VERBOSE
 	AcceptEnv		_XXX_TEST_*
 	AcceptEnv		_XXX_TEST
 	Subsystem	sftp	$SFTPSERVER
-- 
2.45.2