JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... remaining flags listed below. The distinction between these two groups of flags is that the file creation flags affect the semantics of the open operation itself, while the file status flags affect the semantics of subsequent I/O operations. The file stat ... e process. The group ownership (group ID) of the new file is set either to the effective group ID of the process (System V semantics) or to the group ID of the parent directory (BSD semantics). On Linux, the behavior depends on whether the set-group-ID mo ... de bit is set on the parent directory: if that bit is set, then BSD semantics apply; otherwise, System V semantics apply. For some filesystems, the behavior also depends on the bsdgroups and sysvgroup ... ... remaining flags listed below. The distinction between these two groups of flags is that the file creation flags affect the semantics of the open operation itself, while the file status flags affect the semantics of subsequent I/O operations. The file stat ... e process. The group ownership (group ID) of the new file is set either to the effective group ID of the process (System V semantics) or to the group ID of the parent directory (BSD semantics). On Linux, the behavior depends on whether the set-group-ID mo ... de bit is set on the parent directory: if that bit is set, then BSD semantics apply; otherwise, System V semantics apply. For some filesystems, the behavior also depends on the bsdgroups and sysvgroup ... ... remaining flags listed below. The distinction between these two groups of flags is that the file creation flags affect the semantics of the open operation itself, while the file status flags affect the semantics of subsequent I/O operations. The file stat ... e process. The group ownership (group ID) of the new file is set either to the effective group ID of the process (System V semantics) or to the group ID of the parent directory (BSD semantics). On Linux, the behavior depends on whether the set-group-ID mo ... de bit is set on the parent directory: if that bit is set, then BSD semantics apply; otherwise, System V semantics apply. For some filesystems, the behavior also depends on the bsdgroups and sysvgroup ... ... al () wrapper function does not invoke the kernel system call. Instead, it calls sigaction (2) using flags that supply BSD semantics. This default behavior is provided as long as a suitable feature test macro is defined: _BSD_SOURCE on glibc 2.19 and earl ... d; see feature_test_macros (7) for details.) If such a feature test macro is not defined, then signal () provides System V semantics. 関連項目 kill (1), alarm (2), kill (2), pause (2), sigaction (2), signalfd (2), sigpending (2), sigprocmask (2), sigsuspe ... ... daemon process is not a session leader. Instead, the resulting daemon is a session leader. On systems that follow System V semantics (e.g., Linux), this means that if the daemon opens a terminal that is not already a controlling terminal for another sessi ... ... でこのファイルディスクリプターから read (2) を行うと、子プロセスに対するキューに入っているシグナルに関する 情報が返される。 Semantics of file descriptor passing As with other file descriptors, signalfd file descriptors can be passed to another process via ... 体) 宛てのシグナルが読み出される。 (スレッドは同じプロセスの他のスレッド宛てのシグナルを読み出すことはできない。) epoll (7) semantics If a process adds (via epoll_ctl (2)) a signalfd file descriptor to an epoll (7) instance, then epoll_wait (2) returns eve ... ... でこのファイルディスクリプターから read (2) を行うと、子プロセスに対するキューに入っているシグナルに関する 情報が返される。 Semantics of file descriptor passing As with other file descriptors, signalfd file descriptors can be passed to another process via ... 体) 宛てのシグナルが読み出される。 (スレッドは同じプロセスの他のスレッド宛てのシグナルを読み出すことはできない。) epoll (7) semantics If a process adds (via epoll_ctl (2)) a signalfd file descriptor to an epoll (7) instance, then epoll_wait (2) returns eve ... ... .1-2008 (但し、下記のバグの節も参照)。 SCHED_BATCH と SCHED_IDLE ポリシーは Linux 固有である。 注意 Further details of the semantics of all of the above "normal" and "real-time" scheduling policies can be found in the sched (7) manual page. That page also ... ... .1-2008 (但し、下記のバグの節も参照)。 SCHED_BATCH と SCHED_IDLE ポリシーは Linux 固有である。 注意 Further details of the semantics of all of the above "normal" and "real-time" scheduling policies can be found in the sched (7) manual page. That page also ... ... rnel will silently not return any values which would be stored outside the provided space. As with sched_setattr (), these semantics allow for future extensibility of the interface. flags 引数は、このインターフェースの将来の拡張のために用意されている。 現 ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。