Add trace command for reconnect debugging
ci / test (push) Has been cancelled
ci / fuzz-smoke (push) Has been cancelled
ci / windows-client (push) Has been cancelled
ci / package-release (linux-x86_64, ubuntu-latest) (push) Has been cancelled
ci / package-release (macos-aarch64, macos-14) (push) Has been cancelled
ci / package-release (macos-x86_64, macos-13) (push) Has been cancelled
ci / package-release (windows-x86_64, windows-latest) (push) Has been cancelled
ci / remote-bench (push) Has been cancelled

This commit is contained in:
DuProcess
2026-07-12 00:52:47 -04:00
parent 80e922957e
commit 99d54899bd
4 changed files with 289 additions and 11 deletions
+9 -3
View File
@@ -73,12 +73,18 @@ File copy must be enabled by the server config.
For terminal/reconnect bugs, run a client with:
```sh
DOSH_TRACE=/tmp/dosh-client.log DOSH_TRACE_BYTES=1 dosh HOST
dosh trace HOST
```
The client log path is printed before the session starts. To choose it:
```sh
dosh trace --client-log /tmp/dosh-client.log HOST
```
Set `DOSH_TRACE=/tmp/dosh-server.log` on `dosh-server` for matching server
events. `DOSH_TRACE_BYTES=1` records byte prefixes, so use it only for short
reproductions.
events. Trace byte prefixes are enabled for `dosh trace`, so use it only for
short reproductions.
## VS Code