{
    "content": [
        {
            "type": "text",
            "text": "# IPC_NAMESPACES (info)\n\n## NAME\n\nipcnamespaces - overview of Linux IPC namespaces\n\n## DESCRIPTION\n\nIPC  namespaces isolate certain IPC resources, namely, System V IPC ob-\njects (see sysvipc(7)) and (since Linux 2.6.30)  POSIX  message  queues\n(see  mqoverview(7)).   The  common characteristic of these IPC mecha-\nnisms is that IPC objects  are  identified  by  mechanisms  other  than\nfilesystem pathnames.\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION**\n- **SEE ALSO**\n- **COLOPHON**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "IPC_NAMESPACES",
        "section": "",
        "mode": "info",
        "summary": "ipcnamespaces - overview of Linux IPC namespaces",
        "synopsis": null,
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [
            {
                "name": "nsenter",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/nsenter/1/json"
            },
            {
                "name": "unshare",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/unshare/1/json"
            },
            {
                "name": "clone",
                "section": "2",
                "url": "https://www.chedong.com/phpMan.php/man/clone/2/json"
            },
            {
                "name": "setns",
                "section": "2",
                "url": "https://www.chedong.com/phpMan.php/man/setns/2/json"
            },
            {
                "name": "unshare",
                "section": "2",
                "url": "https://www.chedong.com/phpMan.php/man/unshare/2/json"
            },
            {
                "name": "mqoverview",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/mqoverview/7/json"
            },
            {
                "name": "namespaces",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/namespaces/7/json"
            },
            {
                "name": "sysvipc",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/sysvipc/7/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 27,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "COLOPHON",
                "lines": 6,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "ipcnamespaces - overview of Linux IPC namespaces\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "IPC  namespaces isolate certain IPC resources, namely, System V IPC ob-\njects (see sysvipc(7)) and (since Linux 2.6.30)  POSIX  message  queues\n(see  mqoverview(7)).   The  common characteristic of these IPC mecha-\nnisms is that IPC objects  are  identified  by  mechanisms  other  than\nfilesystem pathnames.\n\nEach  IPC namespace has its own set of System V IPC identifiers and its\nown POSIX message queue filesystem.  Objects created in  an  IPC  name-\nspace are visible to all other processes that are members of that name-\nspace, but are not visible to processes in other IPC namespaces.\n\nThe following /proc interfaces are distinct in each IPC namespace:\n\n*  The POSIX message queue interfaces in /proc/sys/fs/mqueue.\n\n*  The System V IPC interfaces in /proc/sys/kernel, namely: msgmax, ms-\ngmnb, msgmni, sem, shmall, shmmax, shmmni, and shmrmidforced.\n\n*  The System V IPC interfaces in /proc/sysvipc.\n\nWhen an IPC namespace is destroyed (i.e., when the last process that is\na member of the namespace terminates), all IPC objects in the namespace\nare automatically destroyed.\n\nUse  of  IPC  namespaces  requires a kernel that is configured with the\nCONFIGIPCNS option.\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "nsenter(1), unshare(1), clone(2), setns(2), unshare(2), mqoverview(7),\nnamespaces(7), sysvipc(7)\n",
                "subsections": []
            },
            "COLOPHON": {
                "content": "This  page  is  part of release 5.10 of the Linux man-pages project.  A\ndescription of the project, information about reporting bugs,  and  the\nlatest     version     of     this    page,    can    be    found    at\nhttps://www.kernel.org/doc/man-pages/.\n\nLinux                             2019-08-02                 IPCNAMESPACES(7)",
                "subsections": []
            }
        }
    }
}