JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... ain(int argc, char *argv[]) { int h; int fd1 = -1, fd2 = -1; char buf1[BUF_SIZE], buf2[BUF_SIZE]; int buf1_avail = 0, buf1_written = 0; int buf2_avail = 0, buf2_written = 0; if (argc != 4) { fprintf(stderr, "Usage\n\tfwd <listen-port> " "<forward-to-por ... d1 is added to exceptfds. */ if (fd2 > 0 && buf2_avail < BUF_SIZE) FD_SET(fd2, &readfds); if (fd1 > 0 && buf2_avail - buf2_written > 0) FD_SET(fd1, &writefds); if (fd2 > 0 && buf1_avail - buf1_written > 0) FD_SET(fd2, &writefds); if (fd1 > 0) { FD_SET(f ... ct sockaddr *) &client_addr, &addrlen); if (fd == -1) { perror("accept()"); } else { SHUT_FD1; SHUT_FD2; buf1_avail = buf1_written = 0; buf2_avail = buf2_written = 0; fd1 = fd; fd2 = connect_socket(forward_port, argv[3]); if (fd2 == -1) SHUT_FD1; else p ... ... RCE syncfs (): _GNU_SOURCE 説明 sync () causes all pending modifications to filesystem metadata and cached file data to be written to the underlying filesystems. syncfs () は sync () と同様だが、オープンされたファイルディスクリプター fd が参照するファイ ... fd が有効なファイルディスクリプターでない。。 EIO An error occurred during synchronization. This error may relate to data written to any file on the filesystem, or on metadata related to the filesystem itself. ENOSPC Disk space was exhausted while sync ... hronizing. ENOSPC , EDQUOT Data was written to a files on NFS or another filesystem which does not allocate space at the time of a write (2) system call, and some pre ... ... RCE syncfs (): _GNU_SOURCE 説明 sync () causes all pending modifications to filesystem metadata and cached file data to be written to the underlying filesystems. syncfs () は sync () と同様だが、オープンされたファイルディスクリプター fd が参照するファイ ... fd が有効なファイルディスクリプターでない。。 EIO An error occurred during synchronization. This error may relate to data written to any file on the filesystem, or on metadata related to the filesystem itself. ENOSPC Disk space was exhausted while sync ... hronizing. ENOSPC , EDQUOT Data was written to a files on NFS or another filesystem which does not allocate space at the time of a write (2) system call, and some pre ... ... とした場合は、エラー EBUSY が発生する。 Note that because of the way the pages of the pipe buffer are employed when data is written to the pipe, the number of bytes that can be written may be less than the nominal size, depending on the size of the write ... iptions.) In this context, the term "write lifetime" means the expected time the data will live on media, before being overwritten or erased. An application may use the different hint values specified below to separate writes into different write classe ... ult value. RWH_WRITE_LIFE_NONE No specific write lifetime is associated with this file or inode. RWH_WRITE_LIFE_SHORT Data written to this inode or via this open file description is expected to have a short lifetime. RWH_WRITE_LIFE_MEDIUM Data written t ... ... とした場合は、エラー EBUSY が発生する。 Note that because of the way the pages of the pipe buffer are employed when data is written to the pipe, the number of bytes that can be written may be less than the nominal size, depending on the size of the write ... iptions.) In this context, the term "write lifetime" means the expected time the data will live on media, before being overwritten or erased. An application may use the different hint values specified below to separate writes into different write classe ... ult value. RWH_WRITE_LIFE_NONE No specific write lifetime is associated with this file or inode. RWH_WRITE_LIFE_SHORT Data written to this inode or via this open file description is expected to have a short lifetime. RWH_WRITE_LIFE_MEDIUM Data written t ... ... が有効なオープンされたディスクリプターでない。 EIO An error occurred during synchronization. This error may relate to data written to some other file descriptor on the same file. Since Linux 4.13, errors from write-back will be reported to all file desc ... riptors that might have written the data which triggered the error. Some filesystems (e.g., NFS) keep close track of which data came through which file de ... ... が有効なオープンされたディスクリプターでない。 EIO An error occurred during synchronization. This error may relate to data written to some other file descriptor on the same file. Since Linux 4.13, errors from write-back will be reported to all file desc ... riptors that might have written the data which triggered the error. Some filesystems (e.g., NFS) keep close track of which data came through which file de ... ... 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 block-based filesystems to use polling of ... t 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 immediately available. If this flag is ... 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 data is always appended to the end of the ... ... 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 block-based filesystems to use polling of ... t 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 immediately available. If this flag is ... 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 data is always appended to the end of the ... ... 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 block-based filesystems to use polling of ... t 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 immediately available. If this flag is ... 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 data is always appended to the end of the ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。