09-26-2008
The RSS column is probably what you want. It's how much memory the program is using "in core". The SIZE column might also be what you want -- it's the amount of memory used by the process, including code, stack, heap, etc., whether or not it's in swap or in core.
10 More Discussions You Might Find Interesting
1. AIX
Hello AIX gurues...
In order to present the statistics of real memory usage I need to know how much real memory is used by the AIX 5L kernel. No the exact figures of course but some close to the reality.
The AIX is running in a 7GB real machine, it has a HACMP configuration and my concern is... (1 Reply)
Discussion started by: daniels
1 Replies
2. AIX
We have 2 Rs6000 S-85
Each initially had/have 6 processors and 8 GIG of RAM each
Node 1 we added 14 processors and 32 GIG of RAM On May 19. (11 days ago)
My memory utilization reporting for node 1 showed a spike in available memory 25-30GB for May 19 to 25 . I kind of expected this because I... (5 Replies)
Discussion started by: Skyybugg
5 Replies
3. UNIX for Dummies Questions & Answers
Is there any meaning on parent process id when it is equal = 1?
It is found that most of the ppid is lower than pid of the same process by 1
when perform ps -ef
but notice that some process's ppid is 1 (2 Replies)
Discussion started by: darkrainbow
2 Replies
4. Solaris
hi
pmap, prstat and ps gives the RSS which is shared memory.
I need to know the consumption of real memory. how to do that?
thx (4 Replies)
Discussion started by: melanie_pfefer
4 Replies
5. AIX
Hi
i am new to aix , we are using aix 5.3 version and model is 510 and 520 model servers. in our servers contains 8 gb ram.
but servers average ram usage is reaching 99.9% , can any body help on this , is any impact if memory usage reach 99.9%.
Regards
Balaji Poola (2 Replies)
Discussion started by: Balajipoola007
2 Replies
6. Solaris
Hi All,
I have just started using SUN Solaris o.s version is :SunOS spdwa013(my server name) 5.8 Generic_117350-61 sun4u sparc SUNW,Sun-Fire-480R
My problem is that i have some processes running on that server they have a PID and a PPID.
But sometimes the PPID for a particular process... (2 Replies)
Discussion started by: usha rao
2 Replies
7. Shell Programming and Scripting
Hi Guys,
I'd like to ask your advice on the following, I've written this script to terminate a given process by name:
#!/bin/bash
echo 'Please enter the process you wish to terminate'
read process
pid=$(pidof $process)
kill -9 $pid
echo $2
to make it safer I want it to reject the... (4 Replies)
Discussion started by: Lora Graham
4 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I am currently trying to pin down a process NAME (could be a cron job or a tty) in Solaris. First I obtained a pid and then a ppid. I want to take the PPID and from there find the program/process that is making the VSH go high (cpu usage). I am currently trying to go up the chain using PS... (2 Replies)
Discussion started by: troystevens
2 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I need your help. I am at a new place, just trying to understand what's going on here. When I do df -h, I see many mounts. But most of them are automount, how do I find the real location?
netappt1:/vol/homet2/sthan
1.7T 1.2T 527G 69% /home/sthan... (4 Replies)
Discussion started by: samnyc
4 Replies
10. UNIX for Advanced & Expert Users
Hello All,
Was recently working on an requirement where we have to search files more than a specific number, following is the example on same.
Let's say file names are test_40000.txt,test_40001.txt and so on till test_99999.txt.
Now requirement was to search from find command only those... (1 Reply)
Discussion started by: RavinderSingh13
1 Replies
CORE(5) File Formats Manual CORE(5)
NAME
core - format of memory image file
SYNOPSIS
#include <sys/param.h>
DESCRIPTION
The UNIX System writes out a memory image of a terminated process when any of various errors occur. See sigvec(2) for the list of reasons;
the most common are memory violations, illegal instructions, bus errors, and user-generated quit signals. The memory image is called
`core' and is written in the process's working directory (provided it can be; normal access controls apply).
The core file consists of the u. area, whose size (in 64 byte `clicks') is defined by the USIZE manifest in the <sys/param.h> file. The
u. area starts with a user structure as given in <sys/user.h>. The rest of the u. area consists of the kernel stack for the terminated
process which includes (among other things) the processor registers at the time of the fault; see the system listings for the format of
this area. The remainder of the core file consists first of the data pages and then the stack pages of the process image. The amount of
data space image in the core file is given (in clicks) by the variable u_dsize in the u. area. If the text segment was not write-only and
and shared it is included as the first etext bytes of the data image where etext is taken from the symbol table of the object file which
generated the memory image. The amount of stack image in the core file is given (in clicks) by the variable u_ssize in the u. area.
In general the debugger adb(1) is sufficient to deal with core images.
SEE ALSO
adb(1), sigvec(2), stack(5)
3rd Berkeley Distribution January 26, 1987 CORE(5)