Curt Sampson wrote:

> I don't know, because I don't know enough about real-time scheduling.
> What I envisioned is something fairly simple that would be easy to
> implement. This probably means no sophisticated negotiation of
> priorities or guarantees of access to the CPU. We'd need some sort
> of basic protection to keep a process from eating up so much of
> the CPU that you can never get on to the machine to kill it, though.

If you want someone to, like log in then in order to implement that,
though, it's no longer real-time :-) Unless you use a hot key on the
console and let someone only run such processes as root (in which case
they cuold be allowed to take out the system anyway)...

	Neil

-- 
Neil A. Carson