There&#x27;s no way to know if a machine you can&#x27;t contact is on the other side of a network partition or if it has died&#x2F;disconnected&#x2F;given up. You could have the client try to persist <i>its</i> state across local reboots, at least to the extent necessary to kill the session (in case the latest crypto state needed to <i>resume</i> couldn&#x27;t be saved before the system died), in which case you would have to kill fewer sessions.