10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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
9. 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
10. 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
CREDENTIALS(7) Linux Programmer's Manual CREDENTIALS(7)
NAME
credentials - process identifiers
DESCRIPTION
Process ID (PID)
Each process has a unique nonnegative integer identifier that is assigned when the process is created using fork(2). A process can obtain
its PID using getpid(2). A PID is represented using the type pid_t (defined in <sys/types.h>).
PIDs are used in a range of system calls to identify the process affected by the call, for example: kill(2), ptrace(2), setpriority(2)
setpgid(2), setsid(2), sigqueue(3), and waitpid(2).
A process's PID is preserved across an execve(2).
Parent Process ID (PPID)
A process's parent process ID identifies the process that created this process using fork(2). A process can obtain its PPID using getp-
pid(2). A PPID is represented using the type pid_t.
A process's PPID is preserved across an execve(2).
Process Group ID and Session ID
Each process has a session ID and a process group ID, both represented using the type pid_t. A process can obtain its session ID using
getsid(2), and its process group ID using getpgrp(2).
A child created by fork(2) inherits its parent's session ID and process group ID. A process's session ID and process group ID are pre-
served across an execve(2).
Sessions and process groups are abstractions devised to support shell job control. A process group (sometimes called a "job") is a collec-
tion of processes that share the same process group ID; the shell creates a new process group for the process(es) used to execute single
command or pipeline (e.g., the two processes created to execute the command "ls | wc" are placed in the same process group). A process's
group membership can be set using setpgid(2). The process whose process ID is the same as its process group ID is the process group leader
for that group.
A session is a collection of processes that share the same session ID. All of the members of a process group also have the same session ID
(i.e., all of the members of a process group always belong to the same session, so that sessions and process groups form a strict two-level
hierarchy of processes.) A new session is created when a process calls setsid(2), which creates a new session whose session ID is the same
as the PID of the process that called setsid(2). The creator of the session is called the session leader.
User and Group Identifiers
Each process has various associated user and groups IDs. These IDs are integers, respectively represented using the types uid_t and gid_t
(defined in <sys/types.h>).
On Linux, each process has the following user and group identifiers:
* Real user ID and real group ID. These IDs determine who owns the process. A process can obtain its real user (group) ID using
getuid(2) (getgid(2)).
* Effective user ID and effective group ID. These IDs are used by the kernel to determine the permissions that the process will have when
accessing shared resources such as message queues, shared memory, and semaphores. On most UNIX systems, these IDs also determine the
permissions when accessing files. However, Linux uses the file system IDs described below for this task. A process can obtain its
effective user (group) ID using geteuid(2) (getegid(2)).
* Saved set-user-ID and saved set-group-ID. These IDs are used in set-user-ID and set-group-ID programs to save a copy of the correspond-
ing effective IDs that were set when the program was executed (see execve(2)). A set-user-ID program can assume and drop privileges by
switching its effective user ID back and forth between the values in its real user ID and saved set-user-ID. This switching is done via
calls to seteuid(2), setreuid(2), or setresuid(2). A set-group-ID program performs the analogous tasks using setegid(2), setregid(2),
or setresgid(2). A process can obtain its saved set-user-ID (set-group-ID) using getresuid(2) (getresgid(2)).
* File system user ID and file system group ID (Linux-specific). These IDs, in conjunction with the supplementary group IDs described
below, are used to determine permissions for accessing files; see path_resolution(7) for details. Whenever a process's effective user
(group) ID is changed, the kernel also automatically changes the file system user (group) ID to the same value. Consequently, the file
system IDs normally have the same values as the corresponding effective ID, and the semantics for file-permission checks are thus the
same on Linux as on other UNIX systems. The file system IDs can be made to differ from the effective IDs by calling setfsuid(2) and
setfsgid(2).
* Supplementary group IDs. This is a set of additional group IDs that are used for permission checks when accessing files and other
shared resources. On Linux kernels before 2.6.4, a process can be a member of up to 32 supplementary groups; since kernel 2.6.4, a
process can be a member of up to 65536 supplementary groups. The call sysconf(_SC_NGROUPS_MAX) can be used to determine the number of
supplementary groups of which a process may be a member. A process can obtain its set of supplementary group IDs using getgroups(2),
and can modify the set using setgroups(2).
A child process created by fork(2) inherits copies of its parent's user and groups IDs. During an execve(2), a process's real user and
group ID and supplementary group IDs are preserved; the effective and saved set IDs may be changed, as described in execve(2).
Aside from the purposes noted above, a process's user IDs are also employed in a number of other contexts:
* when determining the permissions for sending signals--see kill(2);
* when determining the permissions for setting process-scheduling parameters (nice value, real time scheduling policy and priority, CPU
affinity, I/O priority) using setpriority(2), sched_setaffinity(2), sched_setscheduler(2), sched_setparam(2), and ioprio_set(2);
* when checking resource limits; see getrlimit(2);
* when checking the limit on the number of inotify instances that the process may create; see inotify(7).
CONFORMING TO
Process IDs, parent process IDs, process group IDs, and session IDs are specified in POSIX.1-2001. The real, effective, and saved set user
and groups IDs, and the supplementary group IDs, are specified in POSIX.1-2001. The file system user and group IDs are a Linux extension.
NOTES
The POSIX threads specification requires that credentials are shared by all of the threads in a process. However, at the kernel level,
Linux maintains separate user and group credentials for each thread. The NPTL threading implementation does some work to ensure that any
change to user or group credentials (e.g., calls to setuid(2), setresuid(2)) is carried through to all of the POSIX threads in a process.
SEE ALSO
bash(1), csh(1), ps(1), access(2), execve(2), faccessat(2), fork(2), getpgrp(2), getpid(2), getppid(2), getsid(2), kill(2), killpg(2),
setegid(2), seteuid(2), setfsgid(2), setfsuid(2), setgid(2), setgroups(2), setresgid(2), setresuid(2), setuid(2), waitpid(2), euidac-
cess(3), initgroups(3), tcgetpgrp(3), tcsetpgrp(3), capabilities(7), path_resolution(7), unix(7)
COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-06-03 CREDENTIALS(7)