From owner-freebsd-arch  Thu Dec  7 13:47: 8 2000
From owner-freebsd-arch@FreeBSD.ORG  Thu Dec  7 13:47:06 2000
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3])
	by hub.freebsd.org (Postfix) with ESMTP id 1401337B400
	for <arch@FreeBSD.ORG>; Thu,  7 Dec 2000 13:47:04 -0800 (PST)
Received: from gecko (gecko [129.108.5.51])
	by cs.utep.edu (8.10.1/8.10.1) with ESMTP id eB7LkWn25281;
	Thu, 7 Dec 2000 14:46:32 -0700 (MST)
Date: Thu, 7 Dec 2000 14:46:32 -0700 (MST)
From: <janb@cs.utep.edu>
X-Sender:  <janb@gecko>
To: Kirk McKusick <mckusick@mckusick.com>
Cc: <arch@FreeBSD.ORG>
Subject: Re: Getting Kernel Process Information
In-Reply-To: <200012071938.LAA03622@beastie.mckusick.com>
Message-ID: <Pine.GSO.4.30.0012071445580.12857-100000@gecko>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 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



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message