Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Currently I'm using kill-session command, but it looks a bit aggressive and often leave sub-processes running, e.g. I have the following processes running in separate tmux windows:

lighttpd -D -f ~/.lighttpd/default.conf # -D don't go to background
foreman #

and whenever I quit tmux session using kill-session those processes still running, looks like it send them into background for some reason which is a bit unexpected.

share|improve this question

closed as unclear what you're asking by Marcks Thomas, Mokubai, nc4pk, Simon Sheehan, random Oct 23 '13 at 4:44

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question.If this question can be reworded to fit the rules in the help center, please edit the question.

Considering there is a new, better question, I've gone ahead and flagged this for closure as unclear. – Blacklight Shining Oct 21 '13 at 6:02

The only alternative to that is to detach tmux and reattach it later. If you stop tmux (through kill-session or any other means), those processes need to be sent to the background (i.e. become children of init) as there is no longer a tmux process that they are children of.

share|improve this answer
and how is it possible to kill those processes when exiting tmux instead of sending them to the background? – Alp Jun 23 '13 at 11:11
Just exit tmux. – Lars Kotthoff Jun 23 '13 at 11:39
that does not seem to work in my case. i have created a new question:… – Alp Jun 23 '13 at 12:49

Not the answer you're looking for? Browse other questions tagged or ask your own question.