When the last process in an IPC namespace is destroyed, the
IPC objects in that namespace are automatically destroyed.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Reported-by: Cedric Le Goater <clg@fr.ibm.com>
This is more consistent with the term "mounts namespace"
used in the 2008 ACM SIGOPS paper, "Virtual servers
and and checkpoint/restart in mainstream Linux".
(I avoided the "s", because using the plural strikes me
as klunky English, and anyway we don't talk about
the "PIDs namespace" or the "networks namespace", etc..)
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The range is not [-pi/2, pi/2], but [-pi, pi].
(mtk: This error was reported by Nicolas Francois, and
should have been fixed in 3.11, but somewhere along the way,
the fix got lost.)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506299
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
In recent times, a number of other namespace flags have been
added to clone(2). As such, it is no longer clear to use
the generic term "namespace" to refer to the particular
namespace controlled by CLONE_NEWNS; instead, use the
term "mount-point namespace".
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
I submitted a patch to fix this. See the LKML thread
"[patch] Fix type errors in inotify interfaces", 18 Nov 2008
If/when these patches are accepted, the pages need to be updated.
It seems that inotify(7) is wrong here:
"/proc/sys/fs/inotify/max_user_watches
This specifies a limit on the number of watches that can be
associated with each inotify instance."
On my system, the default value for this variable is 8192. But I
cannot create more than 8192 watches in total for the same UID
even when they are on different inotify instances. So I suggest
to rephrase this as: "This specifies an upper limit on the
number of watches that can be created per real user ID."
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
signal(7) provides some further details on the use of real-time
signals by the two Linux threading implementations.
Signed-off-by: Michael Kerrisk <michael.kerrisk@gmail.com>
In EXAMPLE, note that PTHREAD_INHERIT_SCHED is the default for
the inherit scheduler attribute attribute.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Reported-by: Loic Domaigne <tech@domaigne.com>
Loic Domaigne points out that if a system implements
SCHED_SPORADIC (which Linux does not), then other
fields are also specified in sched_param. The simple
solution is just to remove that phrase from the man
page.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Reported-by: Loic Domaigne <tech@domaigne.com>
The SYNOPSIS shows types for arguments and return values, but
these are really just suggestions: since the interfaces are
macros, the compiler won't catch all violations of
the "type rules". Warn the reader of this.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk