From owner-freebsd-hackers Thu Jun 5 10:17:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA25324 for hackers-outgoing; Thu, 5 Jun 1997 10:17:49 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA25292 for ; Thu, 5 Jun 1997 10:17:12 -0700 (PDT) Received: (from pallenby@localhost) by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id TAA25706; Thu, 5 Jun 1997 19:15:54 +0200 (SAT) From: Paul Allenby Message-Id: <199706051715.TAA25706@zibbi.mikom.csir.co.za> Subject: Re: setting a really low priority... In-Reply-To: from Lee Crites at "Jun 5, 97 11:13:05 am" To: leec@adam.adonai.net (Lee Crites) Date: Thu, 5 Jun 1997 19:15:54 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Lee Crites wrote:" > > I'd like to have a few processes running on my system which will get, > and maintain, a fixed priority. > > Yes, I could use nice to change the initial priority. In fact, that is > how I am starting one other process on my system already. > > But this isn't really what I'm looking for. I'm more interested in > porting my real-time code to fbsd. > > [note: in this discussion, a 'higher' priority means the process is more > important, thus will be given more system resources, not that it's > priority number is larger -- which would be a 'lower' priority in my > discussion.] > > My main scheduler task needs to be fixed at a really high priority. It Maybe the rtprio command is what you need. Paul