JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... notify group that identifies filesystem objects by file handles. Note that for the directory entry modification events the reported file handle identifies the modified directory and not the created/deleted/moved child object. The use of FAN_CLASS_CONTENT ... file handle information at the time the event is received. When combined with the flag FAN_REPORT_FID , two records may be reported with events that occur on a non-directory object, one to identify the non-directory object itself and one to identify the ... example, when an event occurs on an unlinked but open file. In that case, with the FAN_REPORT_FID flag, the event will be reported with only one record to identify the non-directory object itself, because there is no directory associated with the event. ... ... different file descriptor on the same file. Since Linux 4.13, errors from write-back come with a promise that they may be reported by subsequent. write () requests, and will be reported by a subsequent fsync (2) (whether or not they were also reported b ... ... ORT_DIR_FID in fanotify_init (2) influences what data structures are returned to the event listener for each event. Events reported to a group initialized with one of these flags will use file handles to identify filesystem objects instead of file descri ... rectories requires setting this flag in the mark mask. See fanotify_mark (2) for additional details. The FAN_ONDIR flag is reported in an event mask only if the fanotify group identifies filesystem objects by file handles. fanotify_event_info_fid 構造体の ... e of info_type field is FAN_EVENT_INFO_TYPE_DFID_NAME , the file_handle identifies the same directory object that would be reported with FAN_EVENT_INFO_TYPE_DFID and the file handle is followed by a null terminated string that identifies the name of a di ... ... ay 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 descriptors that might have written the data which triggered the error. Some filesystems (e.g., NFS) keep clos ... ... ay 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 descriptors that might have written the data which triggered the error. Some filesystems (e.g., NFS) keep clos ... ... option argument (i.e., an option at the end of the command line without an expected argument). Such errors are handled and reported as follows: * By default, getopt () prints an error message on standard error, places the erroneous option character in op ... ... option argument (i.e., an option at the end of the command line without an expected argument). Such errors are handled and reported as follows: * By default, getopt () prints an error message on standard error, places the erroneous option character in op ... ... option argument (i.e., an option at the end of the command line without an expected argument). Such errors are handled and reported as follows: * By default, getopt () prints an error message on standard error, places the erroneous option character in op ... ... option argument (i.e., an option at the end of the command line without an expected argument). Such errors are handled and reported as follows: * By default, getopt () prints an error message on standard error, places the erroneous option character in op ... ... option argument (i.e., an option at the end of the command line without an expected argument). Such errors are handled and reported as follows: * By default, getopt () prints an error message on standard error, places the erroneous option character in op ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。