On 21 January 2015 at 12:01, Nicholas Marriott <nicholas.marri...@gmail.com> 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 not new.
I do not see non-forking option as a workaround. screen, sshd, cron etc. all have a way to start without forking nowdays even if initially they have not provided such option. I suppose in all these cases there were useful deployment scenario that justified the option. In fact non-forking support is so common that tools like Docker or supervisord have not bothered with support for forking servers at all. ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
