Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uwm.edu!ogicse!unicorn!milton!etb
From: etb@milton.u.washington.edu (Eric Bushnell)
Newsgroups: comp.sys.apollo
Subject: process priority system calls
Summary: it rears its head again!
Keywords: setpriority() getpriority() ppri
Message-ID: <19041@milton.u.washington.edu>
Date: 26 Mar 91 01:50:08 GMT
Organization: University of Washington, Seattle
Lines: 32

Yes, I'm still frogging around with this stuff 
(some of you may recall an earlier thread about renice et al).
I have two (2) questions.

I'm trying to write a program that gives users control
over their process priorities without allowing them to
block system processes and without relying on Domain to
make up its own priority mapping. I want it to have the
fine granularity and upper/lower bounds of /com/ppri and
the user id checking of normal /etc/renice.

1) Can anybody tell me about proc2_$set_priority(),
which is what /com/ppri uses? Some call that converts unix 
process IDs to apollo uid's would be handy, too.

For now, I'm using a wrapper around /com/pst and /com/ppri for process
info and manipulation. I thought I could use the
error codes returned by set/getpriority() to test
for process ownership, but I haven't gotten that to work.

2) Have set/getpriority() been modified so that they don't
return the ownership errors?

Has anybody else messed with this stuff, and wanna compare
notes? (OK, so it's three questions)

Thanks, everybody.

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