When running TNOS in screen, disconnecting and
reconnecting from the session can cause "tnos panic -
lost keyboard" errors. These stem from EINTR errors
returned from read() (I assume these happen when the
read() happens to be executing exactly when screen
attaches or detaches). In any case, the following
patch will ignore EINTR returns from keyboard read()
calls, which fixes this for me.
Log in to post a comment.