Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!labrea!sri-unix!quintus!pds From: pds@quintus.uucp (Peter Schachte) Newsgroups: comp.sys.amiga Subject: Re: priorities (was Re: (none)) Message-ID: <140@quintus.UUCP> Date: 28 Jun 88 00:29:50 GMT References: <1814@van-bc.UUCP> <128@quintus.UUCP> <4601@killer.UUCP> <635@osupyr.mast.ohio-state.edu> Sender: news@quintus.UUCP Reply-To: pds@quintus.UUCP (Peter Schachte) Organization: Quintus Computer Systems, Inc. Lines: 15 In article <635@osupyr.mast.ohio-state.edu> vkr@osupyr.mast.ohio-state.edu (Vidhyanath K. Rao) writes: >Finally, if the code executed takes only 2-3ms, the priority is irrelevent. >How do you set clock to 2ms accuracy? Do you have a Cessium clock or like? No, what I meant is: if a clock only takes a few milliseconds to update the display each time it does so, who cares if it runs every second, at priority 20? The question I'm really asking is: can anything go wrong on the Amiga if I have a process running at such a high priority? Suppose it's a really badly written clock, and takes half a second to update the clock every second, running at priority 20. Can it cause the system to crash, or cause read/write errors on a DMA hard disk, or anything else serious? Or is the worst that can happen that I waste some time, and slow down the machine? -Peter Schachte pds@quintus.uucp ..!sun!quintus!pds