Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!meter.cis.ohio-state.edu!martens From: martens@meter.cis.ohio-state.edu (Jeff Martens) Newsgroups: comp.sys.amiga Subject: Re: Suggestion for kill command. Message-ID: <66457@tut.cis.ohio-state.edu> Date: 12 Oct 89 17:39:19 GMT References: <26736@shemp.CS.UCLA.EDU> <7877@cbmvax.UUCP> <1989Oct7.091824.8541@csusac.csus.edu> <32292@auc.UUCP> Sender: news@tut.cis.ohio-state.edu Reply-To: Jeff Martens Organization: Ohio State University Computer and Information Science Lines: 29 In article <32292@auc.UUCP> haj@auc.UUCP (4-Harvey Johnson) writes: >In article <1989Oct7.091824.8541@csusac.csus.edu> rohwerwd@csusac.UUCP (W. David Rohwer) writes: >>I have a suggestion for the next version of the OS. Can you include >>a command to kill a process like the UNIX kill command? It would make it >>easier for me to free up resources if a program goes out to lunch. Also, it >>would prevent me from doing a warm reboot of my machine. >I agree! It would be nice to stop a process like in UNIX instead of rebooting >or, as I sometimes end up doing, opening another window while sacrificing >some memory (thank goodness for multitasking!!!). There was a long discussion of this here a few months ago. Essentially, it can't be done easily because AmigaDOS doesn't have resource tracking, and that's probably not worth adding -- slightly worse response time, not reliable since there's really no way to keep a process from grabbing whatever it wants anyway, and nontrivial implementation effort. >Along those lines, a commmand that tells you what processes are running would >be nice, too. Sometimes I have processes running that I don't even know about >or forgot. Try status. -=- -- Jeff (martens@cis.ohio-state.edu) And for those of us who like to gloat: Green Bay 31, Dallas 13 Va. Tech 12, W. Va. 10