If your computer is barely crawling, you can some processes... but you'll have to start them again later. On a Berkeley system, you can the processes... but you won't be able to raise the priority again later, after the system speeds up, unless you're the .
If you don't need your results right away (and you won't get them, anyway, if the system is crawling!), try stopping some jobs. The best candidates are "CPU-eaters" like, , and any job that runs up a lot of time quickly in the or reports. Start them again, later, and the jobs will take up where they left off.
On other shells - even shells without job control (!) - you can usewith the -STOP signal and either the job number or process ID number. csh and tcsh have a stop command that does this for you. On other shells, if you'd like, you can add an alias named stop to the shell . Later, put the job back into the background with bg, or into the foreground with fg. For example:
alias stop='kill -STOP'bash$
jobs+ Running g++ hugeprog.cc & bash$
stop %1+ Stopped (signal) g++ hugeprog.cc ...later... bash$
bg %1+ g++ hugeprog.cc &