1sys_ipc.h(0P)              POSIX Programmer's Manual             sys_ipc.h(0P)
2
3
4

PROLOG

6       This  manual  page is part of the POSIX Programmer's Manual.  The Linux
7       implementation of this interface may differ (consult the  corresponding
8       Linux  manual page for details of Linux behavior), or the interface may
9       not be implemented on Linux.
10

NAME

12       sys/ipc.h — XSI interprocess communication access structure
13

SYNOPSIS

15       #include <sys/ipc.h>
16

DESCRIPTION

18       The <sys/ipc.h> header is used by three mechanisms for XSI interprocess
19       communication (IPC): messages, semaphores, and shared memory. All use a
20       common structure type, ipc_perm, to pass information used in  determin‐
21       ing permission to perform an IPC operation.
22
23       The <sys/ipc.h> header shall define the ipc_perm structure, which shall
24       include the following members:
25
26
27           uid_t    uid    Owner's user ID.
28           gid_t    gid    Owner's group ID.
29           uid_t    cuid   Creator's user ID.
30           gid_t    cgid   Creator's group ID.
31           mode_t   mode   Read/write permission.
32
33       The <sys/ipc.h> header shall define the uid_t, gid_t, mode_t, and key_t
34       types as described in <sys/types.h>.
35
36       The <sys/ipc.h> header shall define the following symbolic constants.
37
38       Mode bits:
39
40       IPC_CREAT   Create entry if key does not exist.
41
42       IPC_EXCL    Fail if key exists.
43
44       IPC_NOWAIT  Error if request must wait.
45
46       Keys:
47
48       IPC_PRIVATE Private key.
49
50       Control commands:
51
52       IPC_RMID    Remove identifier.
53
54       IPC_SET     Set options.
55
56       IPC_STAT    Get options.
57
58       The  following  shall be declared as a function and may also be defined
59       as a macro. A function prototype shall be provided.
60
61
62           key_t  ftok(const char *, int);
63
64       The following sections are informative.
65

APPLICATION USAGE

67       None.
68

RATIONALE

70       None.
71

FUTURE DIRECTIONS

73       None.
74

SEE ALSO

76       <sys_types.h>
77
78       The System Interfaces volume of POSIX.1‐2017, ftok()
79

81       Portions of this text are reprinted and reproduced in  electronic  form
82       from  IEEE Std 1003.1-2017, Standard for Information Technology -- Por‐
83       table Operating System Interface (POSIX), The Open Group Base  Specifi‐
84       cations  Issue  7, 2018 Edition, Copyright (C) 2018 by the Institute of
85       Electrical and Electronics Engineers, Inc and The Open Group.   In  the
86       event of any discrepancy between this version and the original IEEE and
87       The Open Group Standard, the original IEEE and The Open Group  Standard
88       is  the  referee document. The original Standard can be obtained online
89       at http://www.opengroup.org/unix/online.html .
90
91       Any typographical or formatting errors that appear  in  this  page  are
92       most likely to have been introduced during the conversion of the source
93       files to man page format. To report such errors,  see  https://www.ker‐
94       nel.org/doc/man-pages/reporting_bugs.html .
95
96
97
98IEEE/The Open Group                  2017                        sys_ipc.h(0P)
Impressum