GETPID(2) BSD System Calls Manual GETPID(2)NAME
getpid, getppid -- get parent or calling process identification
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/types.h>
#include <unistd.h>
pid_t
getpid(void);
pid_t
getppid(void);
DESCRIPTION
The getpid() system call returns the process ID of the calling process. Though the ID is guaranteed to be unique, it should NOT be used for
constructing temporary file names, for security reasons; see mkstemp(3) instead.
The getppid() system call returns the process ID of the parent of the calling process.
ERRORS
The getpid() and getppid() system calls are always successful, and no return value is reserved to indicate an error.
SEE ALSO fork(2), getpgrp(2), kill(2), setpgid(2), setsid(2), exec(3)STANDARDS
The getpid() and getppid() system calls are expected to conform to ISO/IEC 9945-1:1990 (``POSIX.1'').
HISTORY
The getpid() function appeared in Version 7 AT&T UNIX.
BSD November 2, 2006 BSD
Check Out this Related Man Page
getpid(2) System Calls Manual getpid(2)NAME
getpid, getpgrp, getppid - Gets the process ID, process group ID, parent process ID
SYNOPSIS
#include <unistd.h>
pid_t getpid( void );
pid_t getpgrp( void );
pid_t getppid( void );
Application developers may want to specify an #include statement for <sys/types.h> before the one for <unistd.h> if programs are being
developed for multiple platforms. The additional #include statement is not required on Tru64 UNIX systems or by ISO or X/Open standards,
but may be required on other vendors' systems that conform to these standards.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
getpid(), getpgrp(), getppid(): POSIX.1, XPG4, XPG4-UNIX
Refer to the standards(5) reference page for more information about industry standards and associated tags.
DESCRIPTION
The getpid() function returns the process ID of the calling process.
The getpgrp() function returns the process group ID of the calling process.
The getppid() function returns the parent process ID of the calling process. When a process is created, its parent process ID is the
process ID of its parent process. If a parent process exits, the parent process IDs of its child processes are changed to the process ID
of the init program.
RELATED INFORMATION
System calls: fork(2), kill(2), setpgid(2), setsid(2), wait(2)
Standards: standards(5) delim off
getpid(2)
Hi im a student,
1st time using unix, currently were writing programs using fork() and identifying differences between the parent child processes. Im finding getpid(), getppid(), retVal confusing and we are moving on to grps now any
sites or information you can supply me to make... (1 Reply)
Can anyone please help me in measuring the system call timings!
How do I do it if I have to measure the timing of an operation, say getpid system call.
What different functions can I use for that and what would be the difference using each of them?
Thanx! (3 Replies)
can anyone tell me the program about how to implement a routine similar to getpid() in C program without using the function getpid(). ie. the program has to find out the pid of the process without using the getpid command. Please do help me in this regards at the earliest. (3 Replies)
Hi i am very new to programming in UNIX and don't understand the difference between a system call and a normal function call. Also can I implement system calls from within a program? If so could someone please give me an example of a system call from within a program. Lastly, when creating a... (1 Reply)
Hi everyone, I have a question about the process management, and deep level system functionality of system calls between SystemD and SystemV? Does SystemD use the same system calls (fork(), exec(), bind() etc...) as SystemV? or Vice Versa? If they both use the same or very very similar sys... (2 Replies)