On 2015-01-21 11:01 +, Nicholas Marriott wrote:
> This all seems like stuff that should be fixed in the other programs
> you mention rather than worked around in tmux. Don't they have a way
> to exempt a process from being killed? Programs have been forking like
> tmux does for 40 years, it's n
On 21 January 2015 at 12:01, Nicholas Marriott
wrote:
> This all seems like stuff that should be fixed in the other programs you
> mention rather than worked around in tmux. Don't they have a way to
> exempt a process from being killed? Programs have been forking like tmux
> does for 40 years, it'
This all seems like stuff that should be fixed in the other programs you
mention rather than worked around in tmux. Don't they have a way to
exempt a process from being killed? Programs have been forking like tmux
does for 40 years, it's not new.
On Wed, Jan 21, 2015 at 11:40:10AM +0100, Igor Buk
Consider running tmux on CoreOS. There when a user logs out from ssh,
that kills all user processes including any background tmux sessions.
The workaround is to run tmux server explicitly. For example, instead
of calling tmux one does something like:
systemd-run --unit "tmux-$USER" --service-type=
On 20 January 2015 at 13:09, Igor Bukanov wrote:
> Hello,
>
> is there an option to start tmux server so the process would not fork
No, I did look at this many moons ago though:
https://github.com/ThomasAdam/tmux-cvs-archived/commit/4ae54388081f3802700eae2ebcd876efcb2714f5.diff
But it's not nee
