a simple yz-encsess2 stress test

yzesd-stresstest.sh

#!/bin/bash

export RUST_LOG=debug
# source repo @ https://github.com/YZITE/encsess2
# git clone https://github.com/YZITE/encsess2
# cd encsess2
# cargo build --release
YZESD2PATH=... # should point at the path where the release binaries reside

echo "spawn server ..."
"${YZESD2PATH}/yzesd2-server" --privkey 1QDGxqyyptm60lrwVUII/mr9w8hWn3G2+3lW3ZAr3JA= --listen 127.0.0.1:9999 &> ~/yzesdserv.log & pid_server=$!
sleep 0.2

echo "run clients ..."
(
  yes | "${YZESD2PATH}/yzesd2-client" --remote-pubkey 3sxb4IPqutINTvsgpyz2df4KNWE2NoADE9B++I6TrDw= --connect '127.0.0.1:9999' & pid1=$!
  sleep 0.1
  yes | "${YZESD2PATH}/yzesd2-client" --remote-pubkey 3sxb4IPqutINTvsgpyz2df4KNWE2NoADE9B++I6TrDw= --connect '127.0.0.1:9999' & pid2=$!
  sleep 0.5
  kill $pid1 $pid2
) &> ~/yzesdclients.log
echo "shutting down ..."
kill $pid_server
# now hope that this stresstest produced some fresh new error condition examples ;-)