1EXIT(3)                    Linux Programmer's Manual                   EXIT(3)
2
3
4

NAME

6       exit - cause normal process termination
7

SYNOPSIS

9       #include <stdlib.h>
10
11       void exit(int status);
12

DESCRIPTION

14       The  exit() function causes normal process termination and the value of
15       status & 0377 is returned to the parent (see wait(2)).
16
17       All functions registered with atexit(3) and on_exit(3) are  called,  in
18       the  reverse  order  of their registration.  (It is possible for one of
19       these functions to use atexit(3) or on_exit(3)  to  register  an  addi‐
20       tional  function  to be executed during exit processing; the new regis‐
21       tration is added to the front of the list of functions that  remain  to
22       be  called.)  If one of these functions does not return (e.g., it calls
23       _exit(2), or kills itself with a signal), then none  of  the  remaining
24       functions is called, and further exit processing (in particular, flush‐
25       ing of stdio(3) streams) is abandoned.  If a function has  been  regis‐
26       tered  multiple  times using atexit(3) or on_exit(3), then it is called
27       as many times as it was registered.
28
29       All open stdio(3) streams are flushed and  closed.   Files  created  by
30       tmpfile(3) are removed.
31
32       The  C standard specifies two constants, EXIT_SUCCESS and EXIT_FAILURE,
33       that may be passed to exit() to  indicate  successful  or  unsuccessful
34       termination, respectively.
35

RETURN VALUE

37       The exit() function does not return.
38

ATTRIBUTES

40       For   an   explanation   of   the  terms  used  in  this  section,  see
41       attributes(7).
42
43       ┌──────────┬───────────────┬─────────────────────┐
44Interface Attribute     Value               
45       ├──────────┼───────────────┼─────────────────────┤
46exit()    │ Thread safety │ MT-Unsafe race:exit │
47       └──────────┴───────────────┴─────────────────────┘
48       The exit() function uses a global variable that is not protected, so it
49       is not thread-safe.
50

CONFORMING TO

52       POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD.
53

NOTES

55       The  behavior  is  undefined  if  one of the functions registered using
56       atexit(3) and on_exit(3) calls either exit() or longjmp(3).  Note  that
57       a  call  to execve(2) removes registrations created using atexit(3) and
58       on_exit(3).
59
60       The use of EXIT_SUCCESS and EXIT_FAILURE is slightly more portable  (to
61       non-UNIX  environments) than the use of 0 and some nonzero value like 1
62       or -1.  In particular, VMS uses a different convention.
63
64       BSD has attempted to standardize exit codes; see the file <sysexits.h>.
65
66       After exit(), the  exit  status  must  be  transmitted  to  the  parent
67       process.  There are three cases:
68
69       ·  If  the  parent has set SA_NOCLDWAIT, or has set the SIGCHLD handler
70          to SIG_IGN, the status is discarded and the child dies immediately.
71
72       ·  If the parent was waiting on the child, it is notified of  the  exit
73          status and the child dies immediately.
74
75       ·  Otherwise, the child becomes a "zombie" process: most of the process
76          resources are recycled, but a slot  containing  minimal  information
77          about  the child process (termination status, resource usage statis‐
78          tics) is retained in process table.  This allows the parent to  sub‐
79          sequently  use waitpid(2) (or similar) to learn the termination sta‐
80          tus of the child; at that point the zombie process slot is released.
81
82       If the implementation supports the SIGCHLD signal, this signal is  sent
83       to  the  parent.   If  the parent has set SA_NOCLDWAIT, it is undefined
84       whether a SIGCHLD signal is sent.
85
86   Signals sent to other processes
87       If the exiting process is a session leader and its controlling terminal
88       is  the  controlling  terminal of the session, then each process in the
89       foreground process group of this controlling terminal is sent a  SIGHUP
90       signal,  and  the terminal is disassociated from this session, allowing
91       it to be acquired by a new controlling process.
92
93       If the exit of the process causes a process group to  become  orphaned,
94       and  if any member of the newly orphaned process group is stopped, then
95       a SIGHUP signal followed by a SIGCONT  signal  will  be  sent  to  each
96       process  in  this  process group.  See setpgid(2) for an explanation of
97       orphaned process groups.
98
99       Except in the above cases, where the signalled processes may  be  chil‐
100       dren  of  the terminating process, termination of a process does not in
101       general cause a signal to be sent to children of  that  process.   How‐
102       ever,  a  process  can  use  the prctl(2) PR_SET_PDEATHSIG operation to
103       arrange that it receives a signal if its parent terminates.
104

SEE ALSO

106       _exit(2),   get_robust_list(2),   setpgid(2),    wait(2),    atexit(3),
107       on_exit(3), tmpfile(3)
108

COLOPHON

110       This  page  is  part of release 4.16 of the Linux man-pages project.  A
111       description of the project, information about reporting bugs,  and  the
112       latest     version     of     this    page,    can    be    found    at
113       https://www.kernel.org/doc/man-pages/.
114
115
116
117Linux                             2017-09-15                           EXIT(3)
Impressum