On Friday 17 June 2005 10:28 am, JCA wrote:
> The bottom line is, is there a way to coax A to keep its OpenSSH
> forked processes alive for a prespecified time, no matter what their
> matching ssh clients in B are doing? Why is it the case that the three
> lines I added to the sshd_config file do not pull it off? Something to
> do with the TCP stack overriding them perhaps?

Would just running screen on the server after you log in do the trick for you?
That's what I do when using my laptop as a client. Works great!

If you lose your connection for any reason, just log back in, issue screen -r,
and pick up where you left off.