From owner-freebsd-hackers Sun Nov 22 22:26:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02157 for freebsd-hackers-outgoing; Sun, 22 Nov 1998 22:26:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02145 for ; Sun, 22 Nov 1998 22:26:39 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA02549 for ; Sun, 22 Nov 1998 22:26:06 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id WAA16613 for ; Sun, 22 Nov 1998 22:26:04 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA02686 for hackers@freebsd.org; Sun, 22 Nov 1998 22:26:03 -0800 (PST) Date: Sun, 22 Nov 1998 22:26:03 -0800 (PST) From: Don Lewis Message-Id: <199811230626.WAA02686@salsa.gv.tsc.tdk.com> To: hackers@FreeBSD.ORG Subject: questions about adding sysctl knobs Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking for some guidance about adding sysctl knobs to the kernel. My immediate task is to allow the new F_SETOWN code that I recently committed to 3.0-current to be tuned by using sysctl instead of having some fairly arbitrary policy decisions hard coded into the kernel. I figure I need two knobs to do this. The first knob would limit the allowable range of arguments to fcntl(F_SETOWN). The limits from most to least restrictive would be: the current process the current process group a process or process group in the current session any process or process group The second knob would control whether credentials are be checked at the time signals are sent. Where should these knobs go in the name space, and what are the other magic values I need to plug into the sysctl infrastructure? Once I get this implemented, I've got another little project that I want to build a sysctl tunable into from the start. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message