JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... employed only if WIFSIGNALED returned true. This macro is not specified in POSIX.1-2001 and is not available on some UNIX implementations (e.g., AIX, SunOS). Therefore, enclose its use inside #ifdef WCOREDUMP ... #endif . WIFSTOPPED( wstatus ) 子プロセスがシグ ... en in a waitable state, then waitid () should zero out the si_pid and si_signo fields of the structure. On Linux and other implementations that adhere to this requirement, it is not necessary to zero out the si_pid field before calling waitid (). However, not a ... ll implementations follow the POSIX.1 specification on this point. 返り値 wait (): 成功すると、終了した子プロセスのプロセスID を返す。 エラー ... ... employed only if WIFSIGNALED returned true. This macro is not specified in POSIX.1-2001 and is not available on some UNIX implementations (e.g., AIX, SunOS). Therefore, enclose its use inside #ifdef WCOREDUMP ... #endif . WIFSTOPPED( wstatus ) 子プロセスがシグ ... en in a waitable state, then waitid () should zero out the si_pid and si_signo fields of the structure. On Linux and other implementations that adhere to this requirement, it is not necessary to zero out the si_pid field before calling waitid (). However, not a ... ll implementations follow the POSIX.1 specification on this point. 返り値 wait (): 成功すると、終了した子プロセスのプロセスID を返す。 エラー ... ... employed only if WIFSIGNALED returned true. This macro is not specified in POSIX.1-2001 and is not available on some UNIX implementations (e.g., AIX, SunOS). Therefore, enclose its use inside #ifdef WCOREDUMP ... #endif . WIFSTOPPED( wstatus ) 子プロセスがシグ ... en in a waitable state, then waitid () should zero out the si_pid and si_signo fields of the structure. On Linux and other implementations that adhere to this requirement, it is not necessary to zero out the si_pid field before calling waitid (). However, not a ... ll implementations follow the POSIX.1 specification on this point. 返り値 wait (): 成功すると、終了した子プロセスのプロセスID を返す。 エラー ... ... iserfs, jfs, vfat, and bpf. RENAME_WHITEOUT (Linux 3.18 以降) This operation makes sense only for overlay/union filesystem implementations. Specifying RENAME_WHITEOUT creates a "whiteout" object at the source of the rename at the same time as performing the ren ... of a union/overlay, the whiteout appears as a character device with a {0,0} device number. (Note that other union/overlay implementations may employ different methods for storing whiteout entries; specifically, BSD union mount employs a separate inode type, DT ... ... iserfs, jfs, vfat, and bpf. RENAME_WHITEOUT (Linux 3.18 以降) This operation makes sense only for overlay/union filesystem implementations. Specifying RENAME_WHITEOUT creates a "whiteout" object at the source of the rename at the same time as performing the ren ... of a union/overlay, the whiteout appears as a character device with a {0,0} device number. (Note that other union/overlay implementations may employ different methods for storing whiteout entries; specifically, BSD union mount employs a separate inode type, DT ... ... iserfs, jfs, vfat, and bpf. RENAME_WHITEOUT (Linux 3.18 以降) This operation makes sense only for overlay/union filesystem implementations. Specifying RENAME_WHITEOUT creates a "whiteout" object at the source of the rename at the same time as performing the ren ... of a union/overlay, the whiteout appears as a character device with a {0,0} device number. (Note that other union/overlay implementations may employ different methods for storing whiteout entries; specifically, BSD union mount employs a separate inode type, DT ... ... r a stream-oriented socket; SOCK_DGRAM , for a datagram-oriented socket that preserves message boundaries (as on most UNIX implementations, UNIX domain datagram sockets are always reliable and don't reorder datagrams); and (since Linux 2.6.4) SOCK_SEQPACKET , f ... ction_socket == -1) { perror("socket"); exit(EXIT_FAILURE); } /* * For portability clear the whole structure, since some * implementations have additional (nonstandard) fields in * the structure. */ memset(&name, 0, sizeof(name)); /* Bind socket to socket name. ... (data_socket == -1) { perror("socket"); exit(EXIT_FAILURE); } /* * For portability clear the whole structure, since some * implementations have additional (nonstandard) fields in * the structure. */ memset(&addr, 0, sizeof(addr)); /* Connect socket to socket ad ... ... e is set by a successful semop (2) call, with the implication that no other interface affects the sempid value. While some implementations conform to the behavior specified in POSIX.1, others do not. (The fault here probably lies with POSIX.1 inasmuch as it lik ... ely failed to capture the full range of existing implementation behaviors.) Various other implementations also update sempid for the other operations that update the value of a semaphore: the SETVAL and SETALL operations, as wel ... ... c version 2.13, the statvfs () function will use information from that field rather than scanning /proc/mounts . The glibc implementations of pathconf(path, _PC_REC_XFER_ALIGN); pathconf(path, _PC_ALLOC_SIZE_MIN); pathconf(path, _PC_REC_MIN_XFER_SIZE); respecti ... ... c version 2.13, the statvfs () function will use information from that field rather than scanning /proc/mounts . The glibc implementations of pathconf(path, _PC_REC_XFER_ALIGN); pathconf(path, _PC_ALLOC_SIZE_MIN); pathconf(path, _PC_REC_MIN_XFER_SIZE); respecti ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。