I haven't tried this in labs, but in other cluster I put the following in 
bash_profile on most machines behind the same bastion:

        screen -DR

Then whenever I connect to that host via bastion over ssh ProxyCommand, it 
reopens the same screen session (including the various shell tabs/windows I 
have within that screen). And when the connection drops or if I disconnect on 
purpose, any commands will keep running in to buffer for when I reconnect.

— Krinkle

On 22 Nov 2014, at 08:06, Mjbmr <[email protected]> wrote:

> Hello,
> 
> The article [[Screen]] on Wikitech is only about how to start a new gnu 
> screen under bash, but is there anyway I can change my default login shell to 
> use my own compiled gnu screen?, the difference the this two is when we're 
> connecting to a bash shell and suddenly the connection drops, we won't be 
> able to reattach to bash, and it keeps running, using gnu screen as default 
> login shell makes us enable to reattach to where we were and it's very easy 
> to use and it's time saving, we can create another window when are attached 
> to a window, the future is not possible when we're connecting to a normal 
> screen under bash unless we deattach from it and create a new one, the reason 
> I want to use my own compiled gnu screen is because the default gnu screen on 
> debian doesn't have some futures like it doesn't support colors. please let 
> me know if there is a possibility to have separate login shells for each 
> instance.
> 
> Thank you,
> -- Mjbmr
> 
> _______________________________________________
> Labs-l mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/labs-l

_______________________________________________
Labs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/labs-l

Reply via email to