From owner-freebsd-current Wed Jul 30 16:19:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA11865 for current-outgoing; Wed, 30 Jul 1997 16:19:07 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA11856 for ; Wed, 30 Jul 1997 16:19:00 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id SAA02017; Wed, 30 Jul 1997 18:32:31 -0400 (EDT) From: Peter Dufault Message-Id: <199707302232.SAA02017@hda.hda.com> Subject: Re: where to put access restriction for scheduling classes In-Reply-To: <199707301443.AAA00985@labs.usn.blaze.net.au> from David Nugent at "Jul 31, 97 00:43:47 am" To: davidn@labs.usn.blaze.net.au (David Nugent) Date: Wed, 30 Jul 1997 18:32:30 -0400 (EDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Just out of curiosity, what type of resource are we actually discussing > here? A limit on which process schedulers the process and descendants can select, to permit other than root to select scheduling policies that could hang the system given a bug or purposeful denial of services attack. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval