JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... tained files of the mount point will be monitored. The events which require that filesystem objects are identified by file handles, such as FAN_CREATE , FAN_ATTRIB , FAN_MOVE , and FAN_DELETE_SELF , cannot be provided as a mask when flags contains FAN_M ... event when the metadata for a file or directory has changed. An fanotify group that identifies filesystem objects by file handles is required. FAN_CREATE (Linux 5.1 以降) Create an event when a file or directory has been created in a marked parent dire ... ctory. An fanotify group that identifies filesystem objects by file handles is required. FAN_DELETE (Linux 5.1 以降) Create an event when a file or directory has been deleted in a marked parent dire ... ... eturned 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 descriptors. read (2) が成功すると、 読み出しバッファーには以下の構造体が 1 ... a_len; __aligned_u64 mask; __s32 fd; __s32 pid; }; In case of an fanotify group that identifies filesystem objects by file handles, you should also expect to receive one or more additional information records of the structure detailed below following th ... r the current event and the offset to the next event in the buffer. Unless the group identifies filesystem objects by file handles, the value of event_len is always FAN_EVENT_METADATA_LEN . For a group that identifies filesystem objects by file handles, ... ... e-max 上限を上書きできる。 /proc/sys/fs/file-nr This (read-only) file contains three numbers: the number of allocated file handles (i.e., the number of files presently opened); the number of free file handles; and the maximum number of file handles (i.e ... ., the same value as /proc/sys/fs/file-max ). If the number of allocated file handles is close to the maximum, you should consider increasing the maximum. Before Linux 2.6, the kernel allocated file handles d ... ynamically, but it didn't free them again. Instead the free file handles were kept in a list for reallocation; the "free file handles" value indicates the size of that list. A large number of fre ... ... e-max 上限を上書きできる。 /proc/sys/fs/file-nr This (read-only) file contains three numbers: the number of allocated file handles (i.e., the number of files presently opened); the number of free file handles; and the maximum number of file handles (i.e ... ., the same value as /proc/sys/fs/file-max ). If the number of allocated file handles is close to the maximum, you should consider increasing the maximum. Before Linux 2.6, the kernel allocated file handles d ... ynamically, but it didn't free them again. Instead the free file handles were kept in a list for reallocation; the "free file handles" value indicates the size of that list. A large number of fre ... ... old binaries (i.e., those linked against glibc versions earlier than 2.14) employed a memcpy () implementation that safely handles the overlapping buffers case (by providing an "older" memcpy () implementation that was aliased to memmove (3)). 関連項目 ... ... ibute. However, POSIX requires that all threads in a process share the same credentials. The NPTL threading implementation handles the POSIX requirements by providing wrapper functions for the various system calls that change process UIDs and GIDs. Thes ... ... ibute. However, POSIX requires that all threads in a process share the same credentials. The NPTL threading implementation handles the POSIX requirements by providing wrapper functions for the various system calls that change process UIDs and GIDs. Thes ... ... ibute. However, POSIX requires that all threads in a process share the same credentials. The NPTL threading implementation handles the POSIX requirements by providing wrapper functions for the various system calls that change process UIDs and GIDs. Thes ... ... ibute. However, POSIX requires that all threads in a process share the same credentials. The NPTL threading implementation handles the POSIX requirements by providing wrapper functions for the various system calls that change process UIDs and GIDs. Thes ... ... ibute. However, POSIX requires that all threads in a process share the same credentials. The NPTL threading implementation handles the POSIX requirements by providing wrapper functions for the various system calls that change process UIDs and GIDs. Thes ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。