From: Mike Fedyk <mfedyk@matchmail.com>
To: Andreas Unterkircher <unki@netshadow.at>
Cc: Rob Love <rml@ximian.com>, linux-kernel@vger.kernel.org
Subject: Re: /proc/meminfo values
Date: Mon, 22 Dec 2003 10:40:31 -0800 [thread overview]
Message-ID: <20031222184031.GO6438@matchmail.com> (raw)
In-Reply-To: <1072107278.1165.36.camel@winsucks>
On Mon, Dec 22, 2003 at 04:34:38PM +0100, Andreas Unterkircher wrote:
> Ok, i'm unterstand :) I will simple multiply the proc values with 1024
> when i want to use them with the cricket-snmp-collector. this seems to
> be exactly enough - i only want to know - thanks rob and rik for the
> info!
You might want to check out the perl script I updated recently in the lrrd
project. It tries to extract as much information from each kernel version
as possible that is presented in /proc/meminfo (and slabinfo for 2.4).
http://cvs.sourceforge.net/viewcvs.py/lrrd/lrrd/client/lrrd.d.linux/memory.in?sortby=date
Mike
prev parent reply other threads:[~2003-12-22 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 14:50 /proc/meminfo values Andreas Unterkircher
2003-12-22 15:18 ` Rik van Riel
2003-12-22 15:31 ` Rob Love
2003-12-22 15:34 ` Andreas Unterkircher
2003-12-22 18:40 ` Mike Fedyk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031222184031.GO6438@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@ximian.com \
--cc=unki@netshadow.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox