JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... 照することができる。 通常のファイルの場合には sendfile () はファイルオフセットを適切に変更する。 返り値 If the transfer was successful, the number of bytes written to out_fd is returned. Note that a successful call to sendfile () may write fewer bytes than ... ... 照することができる。 通常のファイルの場合には sendfile () はファイルオフセットを適切に変更する。 返り値 If the transfer was successful, the number of bytes written to out_fd is returned. Note that a successful call to sendfile () may write fewer bytes than ... ... 功すると、書き込まれたバイト数が返される。エラーの場合、 -1 が返り、 errno にエラーの原因を示す値が設定される。 Note that a successful write () may transfer fewer than count bytes. Such partial writes can occur for various reasons; for example, because ther ... が返る。 注意 The types size_t and ssize_t are, respectively, unsigned and signed integer data types specified by POSIX.1. A successful return from write () does not make any guarantee that data has been committed to disk. On some filesystems, including NFS, ... it does not even guarantee that space has successfully been reserved for the data. In this case, some errors might be delayed until a future write (), fsync (2), or even close ... ... y read /proc/sysvipc/msg to obtain the same information). 返り値 On success, IPC_STAT , IPC_SET , and IPC_RMID return 0. A successful IPC_INFO or MSG_INFO operation returns the index of the highest used entry in the kernel's internal array recording inform ... ion can be used with repeated MSG_STAT or MSG_STAT_ANY operations to obtain information about all queues on the system.) A successful MSG_STAT or MSG_STAT_ANY operation returns the identifier of the queue whose index was given in msqid . エラーの場合は -1 ... ... (7) を参照。 インターフェース 属性 値 pthread_join () Thread safety MT-Safe 準拠 POSIX.1-2001, POSIX.1-2008. 注意 After a successful call to pthread_join (), the caller is guaranteed that the target thread has terminated. The caller may then choose to do ... ... um expected size for a file handle. It is not a guaranteed upper limit as future filesystems may require more space.) Upon successful return, the handle_bytes field is updated to contain the number of bytes actually written to f_handle . The caller can dis ... ount point; that file descriptor can be used in a subsequent call to open_by_handle_at (). mount_id is returned both for a successful call and for a call that results in the error EOVERFLOW . デフォルトでは、 name_to_handle_at () は pathname がシンボリック ... ... um expected size for a file handle. It is not a guaranteed upper limit as future filesystems may require more space.) Upon successful return, the handle_bytes field is updated to contain the number of bytes actually written to f_handle . The caller can dis ... ount point; that file descriptor can be used in a subsequent call to open_by_handle_at (). mount_id is returned both for a successful call and for a call that results in the error EOVERFLOW . デフォルトでは、 name_to_handle_at () は pathname がシンボリック ... ... eturn of zero indicates end of file) and pwrite () returns the number of bytes written. Note that it is not an error for a successful call to transfer fewer bytes than requested (see read (2) and write (2)). エラーの時は -1 が返され、 errno にエラーの原因を ... ... eturn of zero indicates end of file) and pwrite () returns the number of bytes written. Note that it is not an error for a successful call to transfer fewer bytes than requested (see read (2) and write (2)). エラーの時は -1 が返され、 errno にエラーの原因を ... ... eturn of zero indicates end of file) and pwrite () returns the number of bytes written. Note that it is not an error for a successful call to transfer fewer bytes than requested (see read (2) and write (2)). エラーの時は -1 が返され、 errno にエラーの原因を ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。