What if you enable ssh keep alives? Put this in .ssh/config: TCPKeepAlive yes ServerAliveInterval 10
vlock should die on SIGHUP, I don't see it ignoring it in the code. However, this can take a long time on a TCP connection. On Thu, 20 Feb 2020 at 12:50, 'Sven' via tmux-users <[email protected]> wrote: > > yes, it's still active after closing the ssh-connection. i need to open a new > ssh-session, login as root (because "user1" is locked), kill the > vlock-process and finally reset the faillock record of "user1". > > > > Am Donnerstag, 20. Februar 2020 11:37:43 UTC+1 schrieb Nicholas Marriott: >> >> Did you close the terminal containing vlock? vlock should exit in this >> case, if it doesn't it is a vlock bug. Can you see it still running? >> > -- > You received this message because you are subscribed to the Google Groups > "tmux-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/tmux-users/257297e1-0ceb-4647-bbf5-9809fcfcdfad%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "tmux-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/tmux-users/CAEdLfcENmZa9_zxcLN-tZK_VVAP2%2BkjzfpVxOaoQjp%2Bz6jUGSA%40mail.gmail.com.
