12-01-2008
man page for ps:
Quote:
STAT
(s, u, and v flags) Contains the state of the process:
0
Nonexistent
A
Active
I
Intermediate
Z
Canceled
T
Stopped
K
Available kernel process
If the process has memory problems it would bounce to the limits for memory set by the ulimits for the user that started the process.
Nevertheless you could check with vmstat easily if your box has memory problems overall.
8 More Discussions You Might Find Interesting
1. AIX
:confused:
Hello everybody, I am a totel dummy when it comes to UNIX!!!
Must be wondering what I am doing here right?
I'm most keen on knowing about-it-all.
I need help.
Wanna know all about the IBM AIX. The versions, the latest.
Please tell me how do I go about my search.
Thanks a... (3 Replies)
Discussion started by: rtanuja
3 Replies
2. UNIX for Advanced & Expert Users
why IBM-AIX is preferred over HP-UX .....
In what way it is better for infrastructure......?
Suggestions are welcome...
Suggest you read the RULES (0 Replies)
Discussion started by: bishweshwar
0 Replies
3. AIX
hello all,
can anyone send me ibm aix L1 interview questions...
thank u guys...jiyojith (0 Replies)
Discussion started by: jiyojith
0 Replies
4. Programming
hello everybody!!
i want to post a question!
is there any way to get process status using C commands?
To be more specific, i want to know whether a process is running or is stop or killed.
thanks in advance! (3 Replies)
Discussion started by: nicos
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Currently, I'm getting the foll error on an IBM AIX
/etc/profile: 0403-030 The fork function failed. Too many processes already exist.
How can i check the current no. of processes which can run simultaneously on an IBM AIX machine for oracle user and how can i change ?
Thanks
Vin (1 Reply)
Discussion started by: win_vin
1 Replies
6. AIX
Hi,
I want to know whether IBM AIX can be installed on the IBM e series and x series server hardware?
Thanks & Regards
Arun (2 Replies)
Discussion started by: Arun.Kakarla
2 Replies
7. AIX
This is the password aging script for aix just completed. So far tested and still testing on one of our aix server running 5.3.0.0. So anyway as you can see it is very similar to pwage-hpux-T the only difference on aix /etc/passwd file looks in this format. Also for this script to work you need to... (0 Replies)
Discussion started by: sparcguy
0 Replies
8. AIX
Hi There,
I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available).
Anyone could provide me the following answer -
Can IBM VM been deploy on X86 and X64 (Intel Chip)?
If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies
LEARN ABOUT NETBSD
munlockall
MLOCKALL(2) BSD System Calls Manual MLOCKALL(2)
NAME
mlockall, munlockall -- lock (unlock) the address space of a process
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/mman.h>
int
mlockall(int flags);
int
munlockall(void);
DESCRIPTION
The mlockall system call locks into memory the physical pages associated with the address space of a process until the address space is
unlocked, the process exits, or execs another program image.
The following flags affect the behavior of mlockall:
MCL_CURRENT Lock all pages currently mapped into the process's address space.
MCL_FUTURE Lock all pages mapped into the process's address space in the future, at the time the mapping is established. Note that this
may cause future mappings to fail if those mappings cause resource limits to be exceeded.
Since physical memory is a potentially scarce resource, processes are limited in how much they can lock down. A single process can lock the
minimum of a system-wide ``wired pages'' limit and the per-process RLIMIT_MEMLOCK resource limit.
The munlockall call unlocks any locked memory regions in the process address space. Any regions mapped after an munlockall call will not be
locked.
RETURN VALUES
A return value of 0 indicates that the call succeeded and all pages in the range have either been locked or unlocked. A return value of -1
indicates an error occurred and the locked status of all pages in the range remains unchanged. In this case, the global location errno is
set to indicate the error.
ERRORS
mlockall() will fail if:
[EINVAL] The flags argument is zero, or includes unimplemented flags.
[ENOMEM] Locking the indicated range would exceed either the system or per-process limit for locked memory.
[EAGAIN] Some or all of the memory mapped into the process's address space could not be locked when the call was made.
[EPERM] The calling process does not have the appropriate privilege to perform the requested operation.
SEE ALSO
mincore(2), mlock(2), mmap(2), munmap(2), setrlimit(2)
STANDARDS
The mlockall() and munlockall() functions conform to IEEE Std 1003.1b-1993 (``POSIX.1'').
HISTORY
The mlockall() and munlockall() functions first appeared in NetBSD 1.5.
BUGS
The per-process resource limit is a limit on the amount of virtual memory locked, while the system-wide limit is for the number of locked
physical pages. Hence a process with two distinct locked mappings of the same physical page counts as 2 pages against the per-process limit
and as only a single page in the system limit.
BSD
June 12, 1999 BSD