tmux and GNU Screen are well-known utilities which allow multiplexing of virtual consoles. Using either, it is possible to start a session, detach, move to a different machine and resume the session in uninterrupted progress. It’s also possible to use these tools to share a single session between more than one user at the same time.
Basic Sharing with a Single Account
If an account is held jointly between two or more users, then the sharing of the terminal console is very simple. Neither tmux nor screen require anything out of the ordinary for basic sharing between a single account logged in multiple times. Basic sharing is very easy if you are both logged in as the same user.
Basic sharing with screen
In one terminal create a new session for screen, where foobar is the name of your screen session:
screen -S foobar
Then in the other terminal, attach to that session.
screen -x foobar
That’s it, there were just two steps.
Basic sharing with tmux
Again, there are only two steps. In the first terminal, start tmux where shared is the session name:
tmux new-session -s shared
Then in the second terminal attach to the shared session.
tmux attach-session -t shared
Sharing Between Two Different Accounts
Sharing between two different accounts requires some additional steps to grant the privileges necessary for one account to access another’s session. In some cases, it will require help from the system administrator to prepare the setup.
Sharing between two different accounts with tmux
For different users, you have to set the permissions on the tmux socket so that both users can read and write it. There is only one prerequiste, that there be a group in common between the two users. If such a group does not exist it will be necessary to create one.
In the first terminal, start tmux where shared is the session name and shareds is the name of the socket:
tmux -S /tmp/shareds new -s shared
Then chgrp the socket to a group that both users share in common. In this example, joint is the group that both users share. If there are other users in the group, then they also have access. So it might be recommended that the group have only the two members.
chgrp joint /tmp/shareds
In the second terminal attach using that socket and session.
tmux -S /tmp/shareds attach -t shared
That’s it. The session can be made read-only for the second user, but only on a voluntary basis. The decision to work read-only is made when the second user attaches to the session.
tmux -S /tmp/shareds attach -t shared -r
Sharing between two different accounts with screen
If you are logged in as two different users, there are three prerequisites to using screen. First, screen must be set SUID and it is necessary to remove group write access from /var/run/screen. The safety of using SUID in this context is something to consider. Then you must use screen’s ACLs to grant permission to the second user.
sudo chmod u+s /usr/bin/screen
sudo chmod 755 /var/run/screen
In the first user’s terminal, start screen as in the basic sharing above, where foobar is the name of the screen session. Then turn on multiuser mode and add user2 to the ACL, where user2 is the second account to be sharing the session.
screen -S foobar
The session can be made read-only for the second user by entering the following ACL change: ^A:aclchg user2 -w “#?”
Then in the other terminal, attach to the first user’s session.
screen -x user1/foobar
It is also possible to put multiuser on and acladd user2 into .screenrc to have it take effect automatically upon starting screen. If the changes are not desired in all screen sessions, then a separate .screenrc configuration file can be specified by using the -c option when starting screen.
Be careful when exiting. If you just exit the shell, it will end the terminal session for all parties. If you instead detach the session then the other user can continue working uninterrupted. In tmux that is ^B-d and in screen that is ^A-d