Trying regression tests

[Chris Adams]

Once upon a time, Chris Adams <cmadams at hiwaay.net> said:
> I know it is just after a release, but I'm trying to see how the
> regression tests look on Tru64.  I hadn't had a chance to really look at
> them before because I didn't have sudo installed on Tru64 (now I do).
> 
> Anyway, for the 3.9p1 release, all of them run except for a couple of
> problems:
> 
> - agent-ptrace fails; it looks like setgid isn't enough to kill tracing
>   under Tru64, and I can't find anything that looks like it will (like
>   Linux's prctl).

Is there any standard that documents when a process will be traceable?
I don't see anything in SUSv3.  IOW: should this be considered an OS bug
or just an unavailable feature?  I see this test is already skipped for
a couple of OSes, so I guess (at least for now) the suggested patch
would be:

diff -urN openssh-3.9p1-dist/regress/agent-ptrace.sh openssh-3.9p1/regress/agent-ptrace.sh
--- openssh-3.9p1-dist/regress/agent-ptrace.sh	Fri Nov 14 19:13:17 2003
+++ openssh-3.9p1/regress/agent-ptrace.sh	Fri Aug 20 09:44:21 2004
@@ -5,7 +5,7 @@
 
 if have_prog uname ; then
 	case `uname` in
-	AIX|CYGWIN*)
+	AIX|CYGWIN*|OSF1)
 		echo "skipped (not supported on this platform)"
 		exit 0
 		;;

> - reconfigure hangs; the script appears to get stuck in a loop.  I tried
>   turning on shell tracing; it looks like it is hanging when the script
>   is called with "$TEST_SHELL -n $SCRIPT" to check it for errors.  Using
>   TEST_SHELL=/bin/ksh makes it work.

Another way to fix this (without explicitly changing the shell) is to
set the environment variable BIN_SH=xpg4 (this causes calls to /bin/sh
to use a POSIX compliant shell, /bin/ksh, instead of a Bourne shell).
Suggested patch:

diff -urN openssh-3.9p1-dist/regress/test-exec.sh openssh-3.9p1/regress/test-exec.sh
--- openssh-3.9p1-dist/regress/test-exec.sh	Wed Aug 18 17:35:47 2004
+++ openssh-3.9p1/regress/test-exec.sh	Fri Aug 20 09:39:38 2004
@@ -3,6 +3,10 @@
 
 #SUDO=sudo
 
+# For Tru64 to get a POSIX shell
+BIN_SH=xpg4
+export BIN_SH
+
 if [ ! -z "$TEST_SSH_PORT" ]; then
 	PORT="$TEST_SSH_PORT"
 else

-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.