From owner-freebsd-hackers Mon Jul 27 13:38:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03238 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 13:38:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03231 for ; Mon, 27 Jul 1998 13:38:48 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-126.camalott.com [208.229.74.126]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA31406; Mon, 27 Jul 1998 15:39:17 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id PAA17808; Mon, 27 Jul 1998 15:38:04 -0500 (CDT) (envelope-from joelh) Date: Mon, 27 Jul 1998 15:38:04 -0500 (CDT) Message-Id: <199807272038.PAA17808@detlev.UUCP> To: dhw@whistle.com CC: freebsd-hackers@FreeBSD.ORG In-reply-to: <199807271745.KAA25470@pau-amma.whistle.com> (message from David Wolfskill on Mon, 27 Jul 1998 10:45:50 -0700 (PDT)) Subject: Re: Checking RAM From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807271745.KAA25470@pau-amma.whistle.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Could someone tell me how you can check the amount of RAM both available >>> and in use at a given time on FreeBSD 2.2.6 ? > >> Try >> dmesg | more >> soon after a reboot. Should tell you how much RAM was found on the way up. > However, as a follow-on to a discussion I was having with someone else > (where I was doing a bunch of whining about the challenges I was having > in "automatically" being able to determine the configuration of a given > FreeBSD box), the random idea came up that *IF* the kernel could stash > away the results of its probing in some way that might be amenable to > access by suitably-privileged processes at times arbitrarily distant > from re-boot (i.e, scannning logs & output of dmesg won't do the job), > this *might* be sufficiently useful to warrant some effort. I suppose you could add to your own /etc/local: dmesg | egrep '(real|avail) memory = ' > /var/log/mem More generally, you may prefer dmesg > /var/log/dmesg.boot instead. I can't see how this is useful, myself. In a situation where I don't know the configuration of each machine by heart, I use a binder to store configuration info. Helpful in the event of a machine failure. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message