Bash session exits in tmux after some time
by lupe from LinuxQuestions.org on (#6EZNR)
Hi,
I have to access some corporate servers via SSH running RedHat.
I want to leave some processes running inside tmux over the night and to have the output on the screen when I login again in the morning.
Yes, I can redirect to output, but running ansible (at least without filters) outputs escape codes and the log is not nice.
The question is that during the night bash seems to exit and the corresponding tmux panes exit.
If tmux has no open files for editing or there is no other shell like a sqlite3 connection or a tclsh shell, or something else, the whole tmux session exits.
I can't find the cause of this.
What should I be looking for not to have this kind of behavior?
I have to access some corporate servers via SSH running RedHat.
I want to leave some processes running inside tmux over the night and to have the output on the screen when I login again in the morning.
Yes, I can redirect to output, but running ansible (at least without filters) outputs escape codes and the log is not nice.
The question is that during the night bash seems to exit and the corresponding tmux panes exit.
If tmux has no open files for editing or there is no other shell like a sqlite3 connection or a tclsh shell, or something else, the whole tmux session exits.
I can't find the cause of this.
What should I be looking for not to have this kind of behavior?