JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... f the defaults are given later in this man page. * Defining _XOPEN_SOURCE with a value of 600 or greater produces the same effects as defining _POSIX_C_SOURCE with a value of 200112L or greater. Where one sees _POSIX_C_SOURCE >= 200112L in the feature ... test macro requirements in the SYNOPSIS of a man page, it is implicit that the following has the same effect: _XOPEN_SOURCE >= 600 * Defining _XOPEN_SOURCE with a value of 700 or greater produces the same effects as defining _POSIX ... 0809L in the feature test macro requirements in the SYNOPSIS of a man page, it is implicit that the following has the same effect: _XOPEN_SOURCE >= 700 Linux/glibc は以下の機能検査マクロを解釈する: __STRICT_ANSI__ ISO 標準の C。 gcc (1) を -std=c99 や ... ... 7 以降) Provide a per-write equivalent of the O_DSYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_HIPRI (Linux 4.6 以降) High priority read/write. Allows blo ... .7 以降) Provide a per-write equivalent of the O_SYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_NOWAIT (Linux 4.14 以降) Do not wait for data which is not ... 以降) Provide a per-write equivalent of the O_APPEND open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. The offset argument does not affect the write operation; the da ... ... 7 以降) Provide a per-write equivalent of the O_DSYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_HIPRI (Linux 4.6 以降) High priority read/write. Allows blo ... .7 以降) Provide a per-write equivalent of the O_SYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_NOWAIT (Linux 4.14 以降) Do not wait for data which is not ... 以降) Provide a per-write equivalent of the O_APPEND open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. The offset argument does not affect the write operation; the da ... ... 7 以降) Provide a per-write equivalent of the O_DSYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_HIPRI (Linux 4.6 以降) High priority read/write. Allows blo ... .7 以降) Provide a per-write equivalent of the O_SYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_NOWAIT (Linux 4.14 以降) Do not wait for data which is not ... 以降) Provide a per-write equivalent of the O_APPEND open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. The offset argument does not affect the write operation; the da ... ... 7 以降) Provide a per-write equivalent of the O_DSYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_HIPRI (Linux 4.6 以降) High priority read/write. Allows blo ... .7 以降) Provide a per-write equivalent of the O_SYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_NOWAIT (Linux 4.14 以降) Do not wait for data which is not ... 以降) Provide a per-write equivalent of the O_APPEND open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. The offset argument does not affect the write operation; the da ... ... 7 以降) Provide a per-write equivalent of the O_DSYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_HIPRI (Linux 4.6 以降) High priority read/write. Allows blo ... .7 以降) Provide a per-write equivalent of the O_SYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_NOWAIT (Linux 4.14 以降) Do not wait for data which is not ... 以降) Provide a per-write equivalent of the O_APPEND open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. The offset argument does not affect the write operation; the da ... ... 7 以降) Provide a per-write equivalent of the O_DSYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_HIPRI (Linux 4.6 以降) High priority read/write. Allows blo ... .7 以降) Provide a per-write equivalent of the O_SYNC open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. RWF_NOWAIT (Linux 4.14 以降) Do not wait for data which is not ... 以降) Provide a per-write equivalent of the O_APPEND open (2) flag. This flag is meaningful only for pwritev2 (), and its effect applies only to the data range written by the system call. The offset argument does not affect the write operation; the da ... ... ナルが送られる。 pathname で参照されるプログラムファイルに set-user-ID ビットが設定されている場合、呼び出したプロセスの実効 (effective) ユーザー ID は プログラムファイルの所有者 (owner) に変更される。 同様に、プログラムファイルに set-group-ID ビットが設定 ... 呼び出したプロセスの有効グループ ID は プログラムファイルのグループに変更される。 The aforementioned transformations of the effective IDs are not performed (i.e., the set-user-ID and set-group-ID bits are ignored) if any of the following is true: * the ... に使用される。 通常、インタープリターは glibc をリンクしたバイナリでは /lib/ld-linux.so.2 である。 ( ld-linux.so (8) を参照) Effect on process attributes 以下に示す以外のすべてのプロセス属性は execve () の前後で保持される。 * 捕捉されたシグナルの処理方法 ... ... tagram to a datagram socket likewise requires write permission on that socket. POSIX does not make any statement about the effect of the permissions on a socket file, and on some systems (e.g., older BSDs), the socket permissions are ignored. Portable ... own (2) and chmod (2)). 抽象ソケット Socket permissions have no meaning for abstract sockets: the process umask (2) has no effect when binding an abstract socket, and changing the ownership and permissions of the object (via fchown (2) and fchmod (2)) ... has no effect on the accessibility of the socket. Abstract sockets automatically disappear when all open references to the socket are cl ... ... てのオープンされたストリームに対して fclose() を行おうとする処理が含まれていてもよい」 (" abort () may include an attempt to effect fclose() on all open streams") と書かれている。 関連項目 gdb (1), sigaction (2), assert (3), exit (3), longjmp (3), raise ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。