Ok, so there are several options:
You can combine
& to push your script to the background
$ disown [your_script] &
can be checked by the
command. Once typed you will see:
+ Running [your_script]
And the killing can be done by
kill %1, the
1 refers to the job number seen above.
This is the better alternative to
nohup as it does not leave the
nohup.out files littered all over the file system.
Is a "virtual" terminal which you can run from a "real" terminal (actually all terminals today are "virtual" but that is another topic for another day).
Screen will keep running even if your ssh session gets disconnected. Any process which you start in a
screen session will keep running with that screen session. When you reconnect to the server you can reconnect to the screen session and everything will be as if nothing happened, other than the time which passed.
Excellent source: Speaking UNIX: Stayin' alive with Screen".