From: "Martín Marqués" <martin@bugs.unl.edu.ar>
To: "Marc Brekoo" <kernel@brekoo.no-ip.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: howto see shmem
Date: Wed, 24 Oct 2001 20:27:43 -0300 [thread overview]
Message-ID: <20011024232744.F14D62AB49@bugs.unl.edu.ar> (raw)
In-Reply-To: <20011024214017.E5B1D2AB49@bugs.unl.edu.ar> <005001c15ce2$1123aec0$0500a8c0@brekoo.noip.com>
In-Reply-To: <005001c15ce2$1123aec0$0500a8c0@brekoo.noip.com>
On Mié 24 Oct 2001 20:17, Marc Brekoo wrote:
> Hi,
>
> >I have found out that /proc/meminfo doesn't have (at least that's my first
> >thought) info about shared memory (it shows 0, even in heavy duty
> > servers). ipcs also shows nothing, so how can I see the amount of shared
> > memory being used?
> >Th mounted /dev/shmem device also shows 0 kb used (just in case).
>
> AFAIK you can't. Calculating how much shared mem is used in 2.4.x is just
> too hard...
And this:
# ipcs
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 65536 nobody 600 46084 11 dest
------ Semaphore Arrays --------
key semid owner perms nsems status
0x00000000 393216 nobody 600 1
------ Message Queues --------
key msqid owner perms used-bytes messages
#
I can see 46084 bytes in shared memory used by the apache.
Am I wrong?
Saludos... :-)
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-----------------------------------------------------------------
Martín Marqués | mmarques@unl.edu.ar
Programador, Administrador, DBA | Centro de Telematica
Universidad Nacional
del Litoral
-----------------------------------------------------------------
next prev parent reply other threads:[~2001-10-24 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 21:40 Martín Marqués
2001-10-24 23:17 ` Marc Brekoo
2001-10-24 23:27 ` Martín Marqués [this message]
2001-10-24 23:37 ` Robert Love
2001-10-24 23:39 ` Martín Marqués
2001-10-24 23:48 ` Mike Fedyk
2001-10-25 13:34 ` Christoph Rohland
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=20011024232744.F14D62AB49@bugs.unl.edu.ar \
--to=martin@bugs.unl.edu.ar \
--cc=kernel@brekoo.no-ip.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®