1INTRO(2) Linux Programmer's Manual INTRO(2)
2
6 intro - introduction to system calls
7
9 Section 2 of the manual describes the Linux system calls. A system
10 call is an entry point into the Linux kernel. Usually, system calls
11 are not invoked directly: instead, most system calls have corresponding
12 C library wrapper functions which perform the steps required (e.g.,
13 trapping to kernel mode) in order to invoke the system call. Thus,
14 making a system call looks the same as invoking a normal library func‐
15 tion.
16 For a list of the Linux system calls, see syscalls(2).
18
20 On error, most system calls return a negative error number (i.e., the
21 negated value of one of the constants described in errno(3)). The C
22 library wrapper hides this detail from the caller: when a system call
23 returns a negative value, the wrapper copies the absolute value into
24 the errno variable, and returns -1 as the return value of the wrapper.
25 The value returned by a successful system call depends on the call.
27 Many system calls return 0 on success, but some can return nonzero val‐
28 ues from a successful call. The details are described in the individ‐
29 ual manual pages.
30 In some cases, the programmer must define a feature test macro in order
32 to obtain the declaration of a system call from the header file speci‐
33 fied in the man page SYNOPSIS section. (Where required, these feature
34 test macros must be defined before including any header files.) In
35 such cases, the required macro is described in the man page. For fur‐
36 ther information on feature test macros, see feature_test_macros(7).
37
39 Certain terms and abbreviations are used to indicate UNIX variants and
40 standards to which calls in this section conform. See standards(7).
41
43 Calling directly
44 In most cases, it is unnecessary to invoke a system call directly, but
45 there are times when the Standard C library does not implement a nice
46 wrapper function for you. In this case, the programmer must manually
47 invoke the system call using syscall(2). Historically, this was also
48 possible using one of the _syscall macros described in _syscall(2).
49 Authors and copyright conditions
51 Look at the header of the manual page source for the author(s) and
52 copyright conditions. Note that these can be different from page to
53 page!
54
56 _syscall(2), syscall(2), syscalls(2), errno(3), intro(3),
57 capabilities(7), credentials(7), feature_test_macros(7),
58 mq_overview(7), path_resolution(7), pipe(7), pty(7), sem_overview(7),
59 shm_overview(7), signal(7), socket(7), standards(7), svipc(7),
60 symlink(7), time(7)
61
63 This page is part of release 3.53 of the Linux man-pages project. A
64 description of the project, and information about reporting bugs, can
65 be found at http://www.kernel.org/doc/man-pages/.
66Linux 2010-11-11 INTRO(2)