From owner-freebsd-hackers Thu Jun 12 04:07:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA22930 for hackers-outgoing; Thu, 12 Jun 1997 04:07:45 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA22922 for ; Thu, 12 Jun 1997 04:07:41 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA05372; Thu, 12 Jun 1997 07:02:11 -0400 (EDT) From: Peter Dufault Message-Id: <199706121102.HAA05372@hda.hda.com> Subject: Re: rtprio from non-root users ? In-Reply-To: <199706111352.PAA09210@labinfo.iet.unipi.it> from Luigi Rizzo at "Jun 11, 97 03:52:35 pm" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Thu, 12 Jun 1997 07:02:11 -0400 (EDT) Cc: hackers@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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have (yesterday night) implemented a small change to rtprio (check > PRs in the last 24 hours, I don't remember the number) which reads > allowed users from /etc/rtprio.conf . Jordan suggests to use the > login.class database to add a rtprio capability, which seems a much > better approach. I am not very much in favour of modifying the kernel > if the desired functionality can be achieved in userspace. I looked at login.conf and it looks good. I assume it is the same as what I'm doing only general (I'm modifying sysctl settings when you successfully open the device and I assume that is how it works since the resource limits are now there - it is about as much user versus kernel in both cases only with the kernel work done). Thanks and I'll switch over. Unfortunately there is no history or standards sections on the related manpages and so I can't tell where these interfaces come from and how standard they are (I don't have the cvs stuff here). -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval