1ipc_namespaces(7)      Miscellaneous Information Manual      ipc_namespaces(7)
2
3
4

NAME

6       ipc_namespaces - overview of Linux IPC namespaces
7

DESCRIPTION

9       IPC  namespaces isolate certain IPC resources, namely, System V IPC ob‐
10       jects (see sysvipc(7)) and (since Linux 2.6.30)  POSIX  message  queues
11       (see  mq_overview(7)).   The  common characteristic of these IPC mecha‐
12       nisms is that IPC objects  are  identified  by  mechanisms  other  than
13       filesystem pathnames.
14
15       Each  IPC namespace has its own set of System V IPC identifiers and its
16       own POSIX message queue filesystem.  Objects created in  an  IPC  name‐
17       space are visible to all other processes that are members of that name‐
18       space, but are not visible to processes in other IPC namespaces.
19
20       The following /proc interfaces are distinct in each IPC namespace:
21
22       •  The POSIX message queue interfaces in /proc/sys/fs/mqueue.
23
24       •  The System V IPC interfaces in /proc/sys/kernel, namely: msgmax, ms‐
25          gmnb, msgmni, sem, shmall, shmmax, shmmni, and shm_rmid_forced.
26
27       •  The System V IPC interfaces in /proc/sysvipc.
28
29       When an IPC namespace is destroyed (i.e., when the last process that is
30       a member of the namespace terminates), all IPC objects in the namespace
31       are automatically destroyed.
32
33       Use  of  IPC  namespaces  requires a kernel that is configured with the
34       CONFIG_IPC_NS option.
35

SEE ALSO

37       nsenter(1), unshare(1), clone(2), setns(2), unshare(2), mq_overview(7),
38       namespaces(7), sysvipc(7)
39
40
41
42Linux man-pages 6.04              2023-02-05                 ipc_namespaces(7)
Impressum