| Age | Commit message (Collapse) | Author |
|---|
|
existence of a process since it's more portable. Found by jbasney at
ncsa.uiuc.edu; ok tim@
|
|
[multiplex.sh test-exec.sh sshd-log-wrapper.sh]
Add optional capability to log output from regress commands; ok markus@
Use with: make TEST_SSH_LOGFILE=/tmp/regress.log
|
|
[multiplex.sh]
regression tests for new multiplex commands
|
|
support FD passing since multiplex requires it. Noted by tim@
|
|
[regress/envpass.sh regress/multiplex.sh]
more portable env passing tests
|
|
[multiplex.sh]
Use -S for scp/sftp to force the use of the ssh being tested.
ok djm@,markus@
|
|
[regress/multiplex.sh]
shared connection env passing regress test
|
|
enough for slow systems, especially if they don't have a kernel RNG).
|
|
it.
|
|
[regress/multiplex.sh]
Add small description of failing test to failure message; ok djm@
|
|
[regress/multiplex.sh]
Use DATA and COPY for test data rather than hard-coded paths; ok djm@
|
|
[regress/multiplex.sh]
Remove datafile between and after tests, kill sshd rather than wait;
ok djm@
|
|
[multiplex.sh]
Silence multiplex sftp and scp tests. ok markus@
|
|
[regress/Makefile regress/test-exec.sh, added regress/multiplex.sh]
regress test for client multiplexing; ok markus@
|
