Gu1llaum-3 2a1f6d5449 fix: replace sshm process with ssh via syscall.Exec (issue #41) ...

When running `sshm <host>`, the sshm process was staying alive as a parent for the entire SSH session.
History is recorded before SSH starts, so the parent process served no purpose.

Use syscall.Exec() to replace the sshm process in-place with ssh, keeping the same PID. Falls back to exec.Command() on Windows where syscall.Exec is not supported.

2026-02-23 21:48:41 +01:00

7.0 KiB

Raw Blame History

View Raw