I would use a terminal multiplexer - screen being the best known, and tmux being a more recent implementation of the idea. I use tmux, and would recommend you do to.
Basically tmux will run a terminal (or set of terminals) on a computer. If you run it on a remote server, you can disconnect from it without the terminal dying. Then when you login in again later you can reconnect, and see all the output you missed.
To start it the first time, just type
Then, when you want to disconnect, you do
Ctrl-B d (ie press Ctrl-B, then release both keys, and then press d.
When you login again, you can run
and you will reconnect to tmux and see all the output that happened. Note that if you accidentally lose the ssh connection (say your network goes down), tmux will still be running, though it may think it is still attached to a connection. You can tell tmux to detach from the last connection and attach to your new connection by running
tmux attach -d
In fact, you can use the
-d option all the time. On servers, I have this in my
alias tt='tmux attach -d'
So when I login I can just type
tt and reattach. You can go one step further if you want and integrate the command into an alias for ssh. I run a mail client inside tmux on a server, and I have a local alias:
alias maileo='ssh -t mail.example.org tmux attach -d'
This does ssh to the server and runs the command at the end -
tmux attach -d The
-t option ensures that a terminal is started - if a command is supplied then it is not run in a terminal by default. So now I can run
maileo on a local command line and connect to the server, and the tmux session. When I disconnect from tmux, the ssh connection is also killed.
This shows how to use tmux for your specific use case, but tmux can do much more than this. This tmux tutorial will teach you a bit more, and there is plenty more out there.