1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
.\" This page Copyright (C) 1997 Joshua Yelon <jyelon@uiuc.edu>
.\" Distribution subject to the terms of the GPL.
.\" minor fixes by Bernd Eckenfels <ecki@debian.org> 1998-04-18
.\" minor fixes by Bernd Eckenfels <ecki@debian.org> 1998-11-01
.\" significan rewrite by Michael Meskes <meskes@debian.org> 2009-04-06
.TH MEMSTAT 1 "01 November 1998 " "Debian" "Linux Programmer's Manual"
.SH NAME
memstat \- Identify what's using up virtual memory.
.SH SYNOPSIS
.ft B
.B memstat
.RB [ "\-w" ] [ "\-p PID" ]
.br
.SH DESCRIPTION
\fBmemstat\fP lists all accessible processes, executables, and shared libraries
that are using up virtual memory. To get a complete list \fBmemstat\fP has to
be run as root to be able to access the data of all running processes.
First, the processes are listed. An amount of memory is shown along
with a process ID and the name of the executable which the process is
running. The amount of memory shown does not include shared memory:
it only includes memory which is private to that process. So, if a
process is using a shared library like libc, the memory used to hold
that library is not included. The memory used to hold the
executable's text-segment is also not included, since that too is
shareable.
After the processes, the shared objects are listed. The amount of
memory is shown along with the filename of the shared object, followed by a
list of the processes using the shared object. The memory is listed as the
total amount of memory allocated to this object throughout the whole namespace.
In brackets also the amount that is really shared is listed.
Finally, a grand total is shown. Note that this program shows the
amount of \fBvirtual\fP (not real) memory used by the various items.
\fBmemstat\fP gets its input from the /proc filesystem. This must be
compiled into your kernel and mounted for \fBmemstat\fP to work. The
pathnames shown next to the shared objects are determined by scanning
the disk. \fBmemstat\fP uses a configuration file, /etc/memstat.conf,
to determine which directories to scan. This file should include all
the major bin and lib directories in your system, as well as the /dev
directory. If you run an executable which is not in one of these
directories, it will be listed by memstat as ``[0dev]:<inode>''.
.SS Options
The \fB-w\fP switch causes a wide printout: lines are not truncated at
80 columns.
.PP
The \fB-p\fP switch causes \fBmemstat\fP to only print data gathered from
looking at the process with the gicen PID.
.SH NOTES
These reports are intended to help identify programs that are using an
excessive amount of memory, and to reduce overall memory waste.
.PP
.SH FILES
.ta
.nf
/etc/memstat.conf
/proc/*/maps
.fi
.SH "SEE ALSO"
ps(1), top(1), free(1), vmstat(8), lsof(8), /usr/share/doc/memstat/memstat-tutorial.txt.gz
.PP
.SH BUGS
\fBmemstat\fP ignores all devices that just map main memory, though this may
cause \fBmemstat\fP to ignore some memory usage.
Memory used by the kernel itself is not listed.
.SH AUTHOR
Originally written by Joshua Yelon <jyelon@uiuc.edu> and patched by Bernd Eckenfels
<ecki@debian.org>. Taken over and rewritten by Michael Meskes <meskes@debian.org>.
|
