summaryrefslogtreecommitdiff
path: root/regress/usr.bin/ssh/multiplex.sh
AgeCommit message (Expand)Author
2013-05-17Move the setting of DATA and COPY into test-exec.shDarren Tucker
2013-04-22Add tests for -Oforward and -Ocancel for local and remote forwardsDarren Tucker
2013-04-22Write mux master logs to regress.log instead of ssh.log to keep separateDarren Tucker
2013-04-06Split the regress log into 3 parts: the debug output from ssh, the debugDarren Tucker
2012-10-05Use 'kill -0' to test for the presence of a pid since it's more portableDarren Tucker
2012-09-10use -Ocheck and waiting for completions by PID to make multiplexing testDarren Tucker
2012-09-10Log -O cmd output to the log file and make logging consistent with the otherDarren Tucker
2012-09-09Add test for ssh -OstopDarren Tucker
2012-06-01append to rather than truncate test log; bz#2013 from openssh ATDamien Miller
2009-05-05Always specify ssh_config for multiplex tests: prevents breakage causedDarren Tucker
2005-04-25Don't call cleanup in multiplex as test-exec will cleanup anywayDarren Tucker
2005-02-27Add optional capability to log output from regress commands; ok markus@Darren Tucker
2004-11-07regression tests for new multiplex commandsDamien Miller
2004-06-22more portable env passing testsMarkus Friedl
2004-06-18Use -S for scp/sftp to force the use of the ssh being tested. ok djm@,markus@Darren Tucker
2004-06-17shared connection env passing regress testDamien Miller
2004-06-17Add small description of failing test to failure message; ok djm@Darren Tucker
2004-06-17Use and for test data rather than hard-coded paths; ok djm@Darren Tucker
2004-06-17Remove datafile between and after tests, kill sshd rather than wait; ok djm@Darren Tucker
2004-06-16Silence multiplex sftp and scp tests. ok markus@Darren Tucker
2004-06-13regress test for client multiplexing; ok markus@Damien Miller