Step 1: run tmux
Initially, you have a terminal open, with bash running in it. I'll call this the original bash.
tmux from the original bash. Tmux runs two processes: the tmux server and the tmux client. The reason it does that is that you can detach from a tmux session and reattach to it later — this is a core feature of tmux. The tmux client connects to the terminal where the session is attached. The server runs the processes running in the tmux windows. When you detach from a session (
C-b d), the client exits, but the server and the processes running in the session keep running. In addition to the two tmux processes, assuming you haven't started a tmux session yet,
tmux creates a new session containing one window where it runs your shell: that's the second bash.
At this point, the relevant part of the process tree looks like this:
This is from the
pstree command on Linux. To get a similar display on macOS, see https://apple.stackexchange.com/questions/11770/linux-ps-f-tree-view-equivalent-on-osx.
xterm is the terminal where I ran my original bash, and
tmux: client is the tmux client started by running
tmux in the original bash.
tmux: server is the tmux server that the tmux client started, and its child
bash is the second bash, where I ran
On Linux, here's the output of
ps inside tmux:
PID TTY TIME CMD
108 pts/56 00:00:00 bash
153 pts/56 00:00:00 ps
By default, Linux's
ps only shows the processes that are running on the current terminal. That's why I see. On FreeBSD, and I expect also on macOS (I ran this on a machine where my shell is zsh, that's why it shows zsh rather than bash):
19690 0 Is 0:00.36 /usr/local/bin/zsh
20046 0 I+ 0:00.01 tmux: client (/tmp//tmux-1001/default) (tmux)
20049 1 Rs 0:00.06 /usr/local/bin/zsh
20138 1 R+ 0:00.01 ps
The reason the BSD
ps shows more processes is that by default, it shows processes that are attached to any terminal. (The technical term is processes that “have a controlling terminal”.) It doesn't show processes that are not attached to a terminal at all, such as the tmux server.
To see all the processes involved and to get more information about these processes, let's run
ps with a few options. The options to see the relevant data are slightly different on different unix variants. I'll show Linux and FreeBSD; macOS is probably close to FreeBSD but may be a little different. On Linux, here's the output of
ps x -o pid,ppid,tty,comm f, filtered to the relevant processes:
PID PPID TT COMMAND
107 1 ? tmux: server
108 107 pts/1 \_ bash
154 108 pts/1 \_ ps
3 1 ? xterm
6 3 pts/0 \_ bash
105 6 pts/0 \_ tmux: client
And on FreeBSD, with
ps -U $(id -u) -A -o pid,ppid,tty,command -d (on macOS you'll need to remove
-d and you won't get the tree presentation) (again filtered; on FreeBSD I'm logged in remotely so the original zsh is in a terminal provided by
PID PPID TTY COMMAND
19689 19687 - sshd: gilles@pts/0 (sshd)
19690 19689 pts/0 - /usr/local/bin/zsh
20046 19690 pts/0 `-- tmux: client (/tmp//tmux-1001/default) (tmux)
20048 1 - tmux: server (/tmp//tmux-1001/default) (tmux)
20049 20048 pts/1 - /usr/local/bin/zsh
20149 20049 pts/1 `-- ps -U 1001 -A -o pid,ppid,tty,command -d
In both case you can see six processes:
- The terminal emulator that provides
- The original shell, running in
- The tmux client, running in
pts/0, started from the original shell.
- The tmux server. It isn't running in a terminal. Its parent (
PPID) is process 1. (This happens because when the tmux client starts the server, it double-forks: it creates a child process which itself creates child process, then exits immediately. When the intermediate process exits, the grandchild becomes orphaned and is therefore adopted by init, which is process 1.)
- The shell running inside tmux. It's running inside the single tmux window, which is the terminal
ps running inside the shell inside tmux.
Step 2: kill tmux
You kill the tmux process. But which one? We saw above that there are two. We also saw above that on macOS,
ps with no options shows all processes that are running in a terminal. So you saw, and killed, the tmux client. This is equivalent to detaching from the session. The tmux server is still running. That's one of the reasons to use tmux: if the client is killed, for example because the terminal where the client is running goes away, the session keeps running.
Step 3: reattach the session
You can see the existing tmux session with
tmux list-sessions. And you can reattach to it with
tmux attach. If you have several sessions, you can choose which one to attach to by passing the session number after
tmux attach, e.g.
tmux attach 0 to attach to the session that
tmux list-sessions describes as
0: 1 windows (created …) ….
If you want to kill the session without attaching to it, you can use
tmux kill-session. There's even a command
tmux kill-server which kills all the sessions.
Step 4: normal exit
When you press Ctrl+D or enter
exit in the shell inside tmux, the shell exits. When the main process of a tmux window exits, tmux closes the window. When tmux closes the last window, the session exits.
ps) mention that. And if you have a
.tmuxrc, post it as well.
tmuxfrom the shell to run it. As soon as tmux opens in the terminal, I run
ps. When I get the pid of tmux, I run
kill [pid]and then run
psagain. I've never configured tmux so I suppose the
.tmuxrcfile will still be at its default.