Dec 15, '03 10:32:00AM • Contributed by: ericasadun
Earlier hints discuss how to suspend and resume processes via kill -- very helpful to me, because I had been launching apps from Terminal and using ^Z, fg and bg to manage them.
A summary of previous hints:
kill -STOP and kill -CONT allow you to pause and resume CPU-hogging processes. Use the Activity Monitor to discover the Process IDs or ps -ax and grep for the program name.The problem comes when you need to juggle several programs at once. Recently, I've been using MacBochs with FreeDos to run Agenda, while using Microsoft Word and Adobe Acrobat -- all of which hog the CPU. It finally occured to me to set some shell variables. e.g.:
% set WORD=1002 % set AGENDA=4787 % set ACROBAT=603I used these to issue the kill commands. e.g.:
% kill -STOP $ACROBAT % kill -CONT $AGENDANow, when I scroll through my command-line history, I can immediately identify which commands control which programs. It's not rocket science. It's not miraculous. But it is awfully convenient.