John Safranek b06a3b123b wolfsshd: wait for the listener, claim the ports ... start_wolfsshd returns once the daemon accepts connections, not once it has written its pid: wolfSSHd saves the PID file just before tcp_listen(), so a caller connecting straight away could be refused while the daemon's log showed no connection at all. A run also claims its port block rather than only probing it. - wait for the daemon's own "Listening on port" line, matched on its pid so a previous daemon's line in the appended log cannot satisfy it - take a block by creating its lock directory, which mkdir makes atomic, and release it in the teardown; probing alone let two runners pick the same block, and a claim whose owner is gone is treated as stale - check that a pid from the PID file is still a wolfsshd, since kill -0 answers only whether some process owns the number - fail the OpenSSH cert test when mktemp gives it no work dir: an empty one reduced its teardown pattern to every wolfsshd present		2026-09-17 15:04:26 +02:00
..
wolfssh	scp, apps: correct three ssh->error reads	2026-09-14 10:40:48 -07:00
wolfsshd	wolfsshd: wait for the listener, claim the ports	2026-09-17 15:04:26 +02:00
include.am	…
wolfssh-options.c	…