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

Possible Duplicate:
Leave bash script running on remote terminal while not logged in?

Recently, I tried to unzip a 30 gig zip file on a remote system using Putty. As the long unzipping process continued, I closed Putty, assuming that the process would just continue to run on the remote machine.

When I came back later and logged back into the machine again, I realized that the process must have stopped only part way through when I closed Putty. I wasn't expecting that to happen.

My question is, how do I prevent this problem? Can I somehow fire off a process in the background? Or should just setup a one time cronjob that will run the process for me?

share|improve this question

marked as duplicate by quack quixote Apr 4 '10 at 17:26

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

This question has been answered before, see e.g.… or… – akid Apr 4 '10 at 16:57
there's also… and… but i think akid's first link is the closest match with the most direct answer. – quack quixote Apr 4 '10 at 17:24
up vote 3 down vote accepted

nohup or disown (in bash) will allow a process or job to continue in the background after the controlling shell has been killed.

share|improve this answer

You could use gnu screen to run the program, and then re-attach to the session later. Just start screen, then start the unzip process. When you want to disconnect, press Ctrl-A D. Then when you want to re-attach to the screen session use screen -r and it'll re-attach to the previous session.

share|improve this answer

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