JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... d (2) (see fanotify (7)). FAN_REPORT_FID (Linux 5.1 以降) This value allows the receipt of events which contain additional information about the underlying filesystem object correlated to an event. An additional record of type FAN_EVENT_INFO_TYPE_FID encaps ... ulates the information about the object and is included alongside the generic event metadata structure. The file descriptor that is used to repre ... _FID (Linux 5.9 以降) Events for fanotify groups initialized with this flag will contain (see exceptions below) additional information about a directory object correlated to an event. An additional record of type FAN_EVENT_INFO_TYPE_DFID encapsulates the in ... ... anotify 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 the generic fanotify_event_metadata structure within the read buffer: st ... ルドは以下のとおりである。 hdr This is a structure of type fanotify_event_info_header . It is a generic header that contains information used to describe an additional information record attached to the event. For example, when an fanotify file descriptor is ... created using FAN_REPORT_FID , a single information record is expected to be attached to the event with info_type field value of FAN_EVENT_INFO_TYPE_FID . When an fanotify fi ... ... talled. c) Various pieces of signal-related context are saved into a special frame that is created on the stack. The saved information includes: + the program counter register (i.e., the address of the next instruction in the main program that should be exe ... ernate signal stack settings. (If the signal handler was installed using the sigaction (2) SA_SIGINFO flag, then the above information is accessible via the ucontext_t object that is pointed to by the third argument of the signal handler.) d) Any signals sp ... s, control passes to the signal trampoline code. 5. The signal trampoline calls sigreturn (2), a system call that uses the information in the stack frame created in step 1 to restore the thread to its state before the signal handler was called. The thread's ... ... for msqid meaning that any user can employ this operation (just as any user may 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 i ... ndex of the highest used entry in the kernel's internal array recording information about all message queues. (This information can be used with repeated MSG_STAT or MSG_STAT_ANY operations to obtain inform ... ... ルチスレッドプログラムでの使用に適している。 The random_r () function is like random (3), except that instead of using state information maintained in a global variable, it uses the state information in the argument pointed to by buf , which must have been pr ... ... ルチスレッドプログラムでの使用に適している。 The random_r () function is like random (3), except that instead of using state information maintained in a global variable, it uses the state information in the argument pointed to by buf , which must have been pr ... ... ルチスレッドプログラムでの使用に適している。 The random_r () function is like random (3), except that instead of using state information maintained in a global variable, it uses the state information in the argument pointed to by buf , which must have been pr ... ... ルチスレッドプログラムでの使用に適している。 The random_r () function is like random (3), except that instead of using state information maintained in a global variable, it uses the state information in the argument pointed to by buf , which must have been pr ... ... Additionally, the ARM port has a code page full of utility functions. Since it's just a raw page of code, there is no ELF information for doing symbol lookups or versioning. It does provide support for different versions though. For information on this cod ... edded CPU, it can get away with things---some of the object formats it runs aren't even ELF based (they're bFLT/FLAT). For information on this code page, it's best to refer to the public documentation: http://docs.blackfin.uclinux.org/doku.php?id=linux-kern ... eges and not in user space. This is done to match the way HP-UX works. Since it's just a raw page of code, there is no ELF information for doing symbol lookups or versioning. Simply call into the appropriate offset via the branch instruction, for example: b ... ... the file referred to by the file descriptor fd to the disk device (or other permanent storage device) so that all changed information can be retrieved even if the system crashes or is rebooted. This includes writing through or flushing a disk cache if pres ... the device reports that the transfer has completed. As well as flushing the file data, fsync () also flushes the metadata information associated with the file (see inode (7)). fsync () の呼び出しは、ファイルが存在しているディレクトリのエントリーがディスクへ ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。