Prolonging terminal sessions: Difference between revisions

Prolonging terminal sessions (view source)

9 bytes added , 1 year ago

Bureaucrats, cc_docs_admin, cc_staff

2,306

edits

Revision as of 17:35, 21 March 2023 (view source) Stubbsda (talk \| contribs) (→‎TMUX) ← Older edit		Revision as of 17:36, 21 March 2023 (view source) Stubbsda (talk \| contribs) (→‎TMUX) Newer edit →
Line 57:		Line 57:
	If you submit a job with tmux and try to start tmux within the same job, you will get the <tt>lost server</tt> error message. This happens because the <tt>$TMUX</tt> environment variable pointing to the tmux server is propagated to the job. The value of the variable is not valid and you can reset it with: {{Command\|unset TMUX}}		If you submit a job with tmux and try to start tmux within the same job, you will get the <tt>lost server</tt> error message. This happens because the <tt>$TMUX</tt> environment variable pointing to the tmux server is propagated to the job. The value of the variable is not valid and you can reset it with: {{Command\|unset TMUX}}

	However, nested use of tmux is not recommended. To send commands to a nested tmux, one has to hit <tt>Ctrl+B</tt> twice; for example, to create a new window, one has to use <tt>Ctrl+B Ctrl+B C</tt>. Consider using ~~<tt>~~screen~~</tt>~~ inside your job (if you are using tmux on a login node).		However, nested use of tmux is not recommended. To send commands to a nested tmux, one has to hit <tt>Ctrl+B</tt> twice; for example, to create a new window, one has to use <tt>Ctrl+B Ctrl+B C</tt>. Consider using [[#GNU Screen \| screen]] inside your job (if you are using tmux on a login node).