Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!know!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!psuvm!auvm!giampal
From: GIAMPAL@auvm.auvm.edu
Newsgroups: comp.sys.amiga.tech
Subject: Re: Scheduler changed under 2.0?
Message-ID: <90318.082800GIAMPAL@auvm.auvm.edu>
Date: 14 Nov 90 13:27:59 GMT
References: <90312.082534GIAMPAL@auvm.auvm.edu> <15756@cbmvax.commodore.com>
 <90316.091455GIAMPAL@auvm.auvm.edu> <39617@ut-emx.uucp>
 <15822@cbmvax.commodore.com>
Organization: The American University - University Computing Center
Lines: 17


In article <15822@cbmvax.commodore.com>, bj@cbmvax.commodore.com (Brian Jackson)
says:
>'LS' program which would, if asked to do a full, long and sorted
>listing of a *large* directory ( > 200 files or so ), hose something
>internal and cause this "spurts" behavior. Only a reboot would fix it.

Any ideas what causes this sort of behavior?  I mean how does a program
doing something wrong internally (assuming no reads/writes to protected mem)
mess up the rest of the system?   Are we just talking about someone getting
stuck in a tight loop for a little bit (or an infinite loop) and that bogging
the system down?  Still seems a little strange.

BTW, I don't know if you can't talk about it, but no one who would know has
said if the scheduler is changed under 2.0 or not.  Well....?  :-)

--dominic