From owner-freebsd-arch Thu Dec 7 13:55: 5 2000 From owner-freebsd-arch@FreeBSD.ORG Thu Dec 7 13:55:03 2000 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from beastie.mckusick.com (tserver.conference.usenix.org [209.179.127.3]) by hub.freebsd.org (Postfix) with ESMTP id 9A75F37B400 for ; Thu, 7 Dec 2000 13:55:02 -0800 (PST) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.9.3/8.9.3) with ESMTP id NAA04017; Thu, 7 Dec 2000 13:54:43 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200012072154.NAA04017@beastie.mckusick.com> To: janb@cs.utep.edu Subject: Re: Getting Kernel Process Information Cc: arch@FreeBSD.ORG In-Reply-To: Your message of "Thu, 07 Dec 2000 14:46:32 MST." Date: Thu, 07 Dec 2000 13:54:43 -0800 From: Kirk McKusick Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: janb@cs.utep.edu Date: Thu, 7 Dec 2000 14:46:32 -0700 (MST) To: Kirk McKusick cc: Subject: Re: Getting Kernel Process Information In-Reply-To: <200012071938.LAA03622@beastie.mckusick.com> > to user processes. I recognize that there are better ways > to handle these issues. I am just trying to make an What are some of the better ways of handling the issue? JAn See Terry Lambert's commentary on the exporting of the ucred structure that appeared about a week ago on this list for a good overview of the alternatives. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message