On 2014-08-12, Clint Pachl <pa...@ecentryx.com> wrote: > Here's my situation: I ssh into a remote server in my group. From that > server, I connect to an adjacent, local server in the group via the > serial terminal using tip(1) or cu(1). If the ssh connection is > disconnected, the login session to the second server's serial com0 will > remain open/active. > > Is there a reliable, system-wide method or configuration to terminate > the serial session if the ssh connection dies?
It should just work... but it doesn't. When the ssh connection is disconnected, tip/cu will receive a SIGHUP and terminate. This will close the outgoing cua(4) device, de-asserting DTR, which with the usual null modem cable will de-assert DCD at the incoming tty(4) device, which in turn should result in a SIGHUP being sent to the processes on that tty. I don't know offhand why this doesn't work. -- Christian "naddy" Weisgerber na...@mips.inka.de
