From owner-freebsd-hackers Sat Aug 1 22:09:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01924 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 22:09:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01918 for ; Sat, 1 Aug 1998 22:09:28 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) for hackers@FreeBSD.ORG id 0z2qOX-0000GC-00; Sun, 2 Aug 1998 00:09:21 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: Another sysctl question To: hackers@FreeBSD.ORG Date: Sun, 02 Aug 1998 00:09:21 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- kern_sysctl.c is not easy to follow for me ... How can I tell inside a sysctl handler whether or not I've been invoked from userland via a system call or from some other part of the kernel? I want to muck about with what sysctl_kern_proc does when called ultimately from a user process, based on some info in the proc structure. At least the code in kern_proc.c has been a good enough example for me to figure out my previous sysctl question ;-) Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcP0gTeRhT8JRySpAQF0ogP/SyibaVhXqSzotRr1DAwsfCasnoUnGqeP DcvOmmsfPMYvWOOBPAXxLKXBXCc1awZV6XT9Zo28jMhsUGZM5PCngdrCExJv3ltW VSA5iUvJutAi78tY/stZ0I34zHhqEZKFX3ASb6Le9Cd9dvt3t+en7HJA335eYzO0 wncat2X05bs= =WbBW -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message