JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... ブジェクトの実装は専用の tmpfs (5) ファイルシステムを使用する。そのファイルシステムは通常 /dev/shm にマウントされる。 例 The programs below employ POSIX shared memory and POSIX unnamed semaphores to exchange a piece of data. The "bounce" program (which mus ... been modified, the "send" program then prints the contents of the modified shared memory. An example execution of the two programs is the following: $ ./pshm_ucase_bounce /myshm & [1] 270171 $ ./pshm_ucase_send /myshm hello HELLO Further detail about th ... ese programs is provided below. プログラムのソース: pshm_ucase.h The following header file is included by both programs below. Its prim ... ... ブジェクトの実装は専用の tmpfs (5) ファイルシステムを使用する。そのファイルシステムは通常 /dev/shm にマウントされる。 例 The programs below employ POSIX shared memory and POSIX unnamed semaphores to exchange a piece of data. The "bounce" program (which mus ... been modified, the "send" program then prints the contents of the modified shared memory. An example execution of the two programs is the following: $ ./pshm_ucase_bounce /myshm & [1] 270171 $ ./pshm_ucase_send /myshm hello HELLO Further detail about th ... ese programs is provided below. プログラムのソース: pshm_ucase.h The following header file is included by both programs below. Its prim ... ... マットと設定ファイル Describes various human-readable file formats and configuration files. 6 ゲーム Games and funny little programs available on the system. 7 概要、約束事、その他 Overviews or descriptions of various topics, conventions and protocols, ch ... 思議な動作など。 EXAMPLES この関数、ファイル、コマンドをどのように使うかを示す、1〜2 個の例。 For details on writing example programs, see Example programs below. 著者 (AUTHORS) 文書やプログラムの著者の一覧。 著者セクションは極力使用しないこと。 一般的には ... 必要かつ有用である。インターフェースを呼び出す以外に何もしないサンプル プログラムは普通はほとんど役に立たない。 * Example programs should ideally be short (e.g., a good example can often be provided in less than 100 lines of code), though in some cases ... ... et of effective capabilities; and for non-root users, the check uses an empty set of capabilities. This allows set-user-ID programs and capability-endowed programs to easily determine the invoking user's authority. In other words, access () does not answ ... stion: "(assuming I'm a setuid binary) can the user who invoked me read/write/execute this file?", which gives set-user-ID programs the possibility to prevent malicious users from causing them to read files which users shouldn't be able to read. 呼び出し ... ... et of effective capabilities; and for non-root users, the check uses an empty set of capabilities. This allows set-user-ID programs and capability-endowed programs to easily determine the invoking user's authority. In other words, access () does not answ ... stion: "(assuming I'm a setuid binary) can the user who invoked me read/write/execute this file?", which gives set-user-ID programs the possibility to prevent malicious users from causing them to read files which users shouldn't be able to read. 呼び出し ... ... et of effective capabilities; and for non-root users, the check uses an empty set of capabilities. This allows set-user-ID programs and capability-endowed programs to easily determine the invoking user's authority. In other words, access () does not answ ... stion: "(assuming I'm a setuid binary) can the user who invoked me read/write/execute this file?", which gives set-user-ID programs the possibility to prevent malicious users from causing them to read files which users shouldn't be able to read. 呼び出し ... ... である)。 現在の実装では、プロセスごとの 共有メモリーセグメントの最大数 ( SHMSEG ) に関する実装依存の制限はない。 例 The two programs shown below exchange a string using a shared memory segment. Further details about the programs are given below. First, we ... writer: Hello, world プログラムのソース: svshm_string.h The following header file is included by the "reader" and "writer" programs. #include < sys/types.h > #include < sys/ipc.h > #include < sys/shm.h > #include < sys/sem.h > #include < stdio.h > #inclu ... ... である)。 現在の実装では、プロセスごとの 共有メモリーセグメントの最大数 ( SHMSEG ) に関する実装依存の制限はない。 例 The two programs shown below exchange a string using a shared memory segment. Further details about the programs are given below. First, we ... writer: Hello, world プログラムのソース: svshm_string.h The following header file is included by the "reader" and "writer" programs. #include < sys/types.h > #include < sys/ipc.h > #include < sys/shm.h > #include < sys/sem.h > #include < stdio.h > #inclu ... ... である)。 現在の実装では、プロセスごとの 共有メモリーセグメントの最大数 ( SHMSEG ) に関する実装依存の制限はない。 例 The two programs shown below exchange a string using a shared memory segment. Further details about the programs are given below. First, we ... writer: Hello, world プログラムのソース: svshm_string.h The following header file is included by the "reader" and "writer" programs. #include < sys/types.h > #include < sys/ipc.h > #include < sys/shm.h > #include < sys/sem.h > #include < stdio.h > #inclu ... ... ge. バージョン These functions first appeared in glibc in version 2.1. Since glibc 2.27, the use of these functions in new programs is no longer supported. 属性 この節で使用されている用語の説明については、 attributes (7) を参照。 インターフェース 属性 値 ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。