From owner-freebsd-security Wed Sep 8 3:37: 0 1999 Delivered-To: freebsd-security@freebsd.org Received: from metriclient-1.uoregon.edu (metriclient-1.uoregon.edu [128.223.172.1]) by hub.freebsd.org (Postfix) with ESMTP id 0378814E75 for ; Wed, 8 Sep 1999 03:36:52 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by metriclient-1.uoregon.edu (8.9.1/8.8.7) id DAA24713; Wed, 8 Sep 1999 03:35:50 -0700 (PDT) Message-ID: <19990908033550.02417@hydrogen.fircrest.net> Date: Wed, 8 Sep 1999 03:35:50 -0700 From: John-Mark Gurney To: "Vladimir Mencl, MK, susSED" Cc: freebsd-security@FreeBSD.ORG Subject: Re: Q: Why is idprio only for root References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Vladimir Mencl, MK, susSED on Wed, Sep 08, 1999 at 12:12:57PM +0200 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Vladimir Mencl, MK, susSED scribbled this message on Sep 8: > Why is the idprio(1) command available only to the superuser? > > What where the reasons? > > It just seems to me that it's no evil to let users run some computations > on the idle priority.... when they want to load the system less then > with a nice(1). because there is a situation where a idle prio process can obtain a lock on a vnode or other kernel resource, but never get the chance to run again while a higher level process continues working... do a search of the mailing lists on this topic... it shouldn't be hard to turn up... it would most likely be on -hackers -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message