Path: utzoo!news-server.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!milton!etb
From: etb@milton.u.washington.edu (Eric Bushnell)
Newsgroups: comp.sys.apollo
Subject: Re: process priorities (problem?)
Keywords: nice process priority foobar
Message-ID: <18175@milton.u.washington.edu>
Date: 11 Mar 91 18:15:23 GMT
References: <1991Mar10.121848.8362@agate.berkeley.edu> <5049bf48.1bc5b@pisa.citi.umich.edu> <1991Mar11.125346.10038@agate.berkeley.edu>
Organization: University of Washington, Seattle
Lines: 26

Thanks, Steve Valentine,for the helpful explanation.

What I'm planning to do is restrict execution rights
on /etc/renice, and then write a wrapper for it
that will not allow negative priorities.

That won't stop determined hackers, as someone else
pointed out, but it's a start. And it's a hint
to cpu-greedy users.

What I'd like now is a way to control such processes
once they've started. If the priority is high enough,
it blocks crp and rlogin, so that I can't renice it
after the fact. Are there any low-level calls
that could be used to signal (kill) and adjust
priorities from another node? It's an odd feature,
of course, but if anybody can renice anything, who
knows what else is possible?

And thanks, all, for the stimulating discussion.


Eric Bushnell                  etb@milton.u.washington.edu
				etb@zeus.ce.washington.edu
University of Washington
Civil Engineering