From owner-freebsd-hackers Mon Apr 3 14:30:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 1AD3637B559 for ; Mon, 3 Apr 2000 14:30:50 -0700 (PDT) (envelope-from mbac@nyct.net) Received: from bsd1.nyct.net (mbac@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id RAA15173; Mon, 3 Apr 2000 17:30:44 -0400 (EDT) (envelope-from mbac@nyct.net) Received: from localhost (mbac@localhost) by bsd1.nyct.net (8.8.8/8.9.3) with ESMTP id RAA00463; Mon, 3 Apr 2000 17:30:44 -0400 (EDT) (envelope-from mbac@nyct.net) X-Authentication-Warning: bsd1.nyct.net: mbac owned process doing -bs Date: Mon, 3 Apr 2000 17:30:44 -0400 (EDT) From: Michael Bacarella To: visi0n Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ProcFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, visi0n wrote: > I was thinking how normal programs get info about cpu and memory > utilization in bsd's systems, (maybe sysctl ?). In the olden days, you used to have to read kernel data structures through /dev/mem (or friends(?)). This usually means that you have to be privileged or at least loved by a privileged person on the system. Lately, a lot (more) of this data is accessible through sysctl, although I don't know exactly what. Just more. Michael Bacarella New York Connect Net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message