Just FYI, Ctrl+z is more than just a stop - it's a pause (specifically SIGTSTP) for the currently running process; by contrast, Ctrl+c is an abort (specifically SIGINT), which ends and closes the process.
After typing Ctrl+z, you should generally decide where you want to run the process by typing either fg (to bring it back to the foreground and resume it) or bg (run it in the background); if you don't do either, then it'll just hang out in memory waiting for permission to continue.
You can see the complete list of jobs running on that shell by typing jobs; their status is listed there as well. To resume a job, typing %n where n is the process number in the jobs list.
Long story short, you don't want to confuse Ctrl+z and Ctrl+c: the latter aborts the process, but the former leaves it idling in memory.
Great post!
Just FYI,
Ctrl+zis more than just a stop - it's a pause (specificallySIGTSTP) for the currently running process; by contrast,Ctrl+cis an abort (specificallySIGINT), which ends and closes the process.After typing
Ctrl+z, you should generally decide where you want to run the process by typing eitherfg(to bring it back to the foreground and resume it) orbg(run it in the background); if you don't do either, then it'll just hang out in memory waiting for permission to continue.You can see the complete list of jobs running on that shell by typing
jobs; their status is listed there as well. To resume a job, typing%nwherenis the process number in thejobslist.Long story short, you don't want to confuse
Ctrl+zandCtrl+c: the latter aborts the process, but the former leaves it idling in memory.Beat me to it.
ctrl+z,bg, andfgwere indispensable to me when I started.Maybe less so now that everyone starts out in xwindows, but I still forget a trailing
&every now and then.