From owner-freebsd-hackers Mon Mar 25 16:32:53 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from damnhippie.dyndns.org (12-253-177-2.client.attbi.com [12.253.177.2]) by hub.freebsd.org (Postfix) with ESMTP id ED0E537B405 for ; Mon, 25 Mar 2002 16:32:48 -0800 (PST) Received: from [172.22.42.2] (peace.hippie.lan [172.22.42.2]) by damnhippie.dyndns.org (8.11.6/8.11.6) with ESMTP id g2Q0WmU06428 for ; Mon, 25 Mar 2002 17:32:48 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Mon, 25 Mar 2002 17:32:59 -0700 Subject: Re: idprio From: Ian To: freebsd-hackers Message-ID: In-Reply-To: <3C9FB98C.BB0F4621@mindspring.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> >> The client already has an option to control the priority: > [ ... ] >> -p Priority (-20=aggressive, 20=passive) [Integer] Optional >> default = 20 >> range from -20 to 20 > > You may also want to consider "idleprio". > Speaking of idprio... I liked the good old days (3.x) when you didn't have to be root to use the command. Given that idprio can be used to raise priorities as well as lower them, I can see the point of having some restrictions, but shouldn't it be possible to structure the code such that a non-root user can lower but not raise the priority on a process they own? I'll even volunteer to do the work unless there's some good reason (technical or policy-wise) why it can't be done. -- Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message