JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... 対しては iopl (2) 関数を使わなければならなかった。Linux 2.6.8 以降では、65,536 個の I/O ポートを指定できる。 Permissions are inherited by the child created by fork (2) (but see NOTES). Permissions are preserved across execve (2); this is useful for giving p ... ioports ファイルには、現在このシステムに割り当てられている I/O ポートが表示される。 Before Linux 2.4, permissions were not inherited by a child created by fork (2). glibc2 には < sys/io.h > と < sys/perm.h > の両方に ioperm () のプロトタイプがある。 後者は ... ... 消される。 Alternatively, if the parent directory has a default ACL (see acl (5)), the umask is ignored, the default ACL is inherited, the permission bits are set based on the inherited ACL, and permission bits absent in the mode argument are turned off. F ... ... bably crash the system, and is not recommended. Prior to Linux 3.7, on some architectures (such as i386), permissions were inherited by the child produced by fork (2) and were preserved across execve (2). This behavior was inadvertently changed in Linux 3 ... ... ling process "immediately". Any open file descriptors belonging to the process are closed. Any children of the process are inherited by init (1) (or by the nearest "subreaper" process as defined through the use of the prctl (2) PR_SET_CHILD_SUBREAPER oper ... ... ling process "immediately". Any open file descriptors belonging to the process are closed. Any children of the process are inherited by init (1) (or by the nearest "subreaper" process as defined through the use of the prctl (2) PR_SET_CHILD_SUBREAPER oper ... ... ling process "immediately". Any open file descriptors belonging to the process are closed. Any children of the process are inherited by init (1) (or by the nearest "subreaper" process as defined through the use of the prctl (2) PR_SET_CHILD_SUBREAPER oper ... ... 部分 (critical section) 内では書き込み時コピーによる ページフォールトさえも発生しないことが保証される。 Memory locks are not inherited by a child created via fork (2) and are automatically removed (unlocked) during an execve (2) or when the process terminat ... es. The mlockall () MCL_FUTURE and MCL_FUTURE | MCL_ONFAULT settings are not inherited by a child created via fork (2) and are cleared during an execve (2). Note that fork (2) will prepare the address space fo ... ... 部分 (critical section) 内では書き込み時コピーによる ページフォールトさえも発生しないことが保証される。 Memory locks are not inherited by a child created via fork (2) and are automatically removed (unlocked) during an execve (2) or when the process terminat ... es. The mlockall () MCL_FUTURE and MCL_FUTURE | MCL_ONFAULT settings are not inherited by a child created via fork (2) and are cleared during an execve (2). Note that fork (2) will prepare the address space fo ... ... 部分 (critical section) 内では書き込み時コピーによる ページフォールトさえも発生しないことが保証される。 Memory locks are not inherited by a child created via fork (2) and are automatically removed (unlocked) during an execve (2) or when the process terminat ... es. The mlockall () MCL_FUTURE and MCL_FUTURE | MCL_ONFAULT settings are not inherited by a child created via fork (2) and are cleared during an execve (2). Note that fork (2) will prepare the address space fo ... ... 部分 (critical section) 内では書き込み時コピーによる ページフォールトさえも発生しないことが保証される。 Memory locks are not inherited by a child created via fork (2) and are automatically removed (unlocked) during an execve (2) or when the process terminat ... es. The mlockall () MCL_FUTURE and MCL_FUTURE | MCL_ONFAULT settings are not inherited by a child created via fork (2) and are cleared during an execve (2). Note that fork (2) will prepare the address space fo ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。