JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... ドレスのポートに対しては iopl (2) 関数を使わなければならなかった。Linux 2.6.8 以降では、65,536 個の I/O ポートを指定できる。 Permissions are inherited by the child created by fork (2) (but see NOTES). Permissions are preserved across execve (2); this is usefu ... l for giving port access permissions to unprivileged programs. このシステムコールはほとんど i386 アーキテクチャーのためだけのものである。 その他の多くのアーキテ ... ならない。 注意 /proc/ioports ファイルには、現在このシステムに割り当てられている I/O ポートが表示される。 Before Linux 2.4, permissions were not inherited by a child created by fork (2). glibc2 には < sys/io.h > と < sys/perm.h > の両方に ioperm () のプロトタ ... ... 入力値よりも大きい場合、 sun_path に終端の NULL バイトが存在する保証はない (「バグ」を参照)。 Pathname socket ownership and permissions In the Linux implementation, pathname sockets honor the permissions of the directory they are in. Creation of a new socket ... tagram socket likewise requires write permission on that socket. POSIX does not make any statement about the effect of the permissions on a socket file, and on some systems (e.g., older BSDs), the socket permissions are ignored. Portable programs should not ... reating a new socket, the owner and group of the socket file are set according to the usual rules. The socket file has all permissions enabled, other than those that are turned off by the process umask (2). The owner, group, and permissions of a pathname so ... ... ットで指定した値に変更する。 通常のスレッドの I/O 特権レベルは 0 である。許可 (permissions) は親から子に継承される。 This call is deprecated, is significantly slower than ioperm (2), and is only provided for older ... el. This will probably crash the system, and is not recommended. Prior to Linux 3.7, on some architectures (such as i386), permissions were inherited by the child produced by fork (2) and were preserved across execve (2). This behavior was inadvertently cha ... ... rocess has both a filesystem group ID and an effective group ID. The (Linux-specific) filesystem group ID is used for permissions checking when accessing filesystem objects, while the effective group ID is used for some other kinds of permissions check ... ... rocess has both a filesystem group ID and an effective group ID. The (Linux-specific) filesystem group ID is used for permissions checking when accessing filesystem objects, while the effective group ID is used for some other kinds of permissions check ... ... ds データ構造体は < sys/msg.h > で以下のように定義されている: struct msqid_ds { struct ipc_perm msg_perm; /* Ownership and permissions */ time_t msg_stime; /* Time of last msgsnd (2) */ time_t msg_rtime; /* Time of last msgrcv (2) */ time_t msg_ctime; /* Ti ... sgid_ds 構造体のフィールドは以下の通りである: msg_perm This is an ipc_perm structure (see below) that specifies the access permissions on the message queue. msg_stime 最後の msgsnd (2) システムコールの時刻。 msg_rtime 最後の msgrcv (2) システムコールの時刻。 ... __seq; /* シーケンス番号 */ }; The least significant 9 bits of the mode field of the ipc_perm structure define the access permissions for the message queue. The permission bits are as follows: 0400 ユーザーによる読み出し 0200 ユーザーによる書き込み 0040 グ ... ... rocess has both a filesystem user ID and an effective user ID. The (Linux-specific) filesystem user ID is used for permissions checking when accessing filesystem objects, while the effective user ID is used for various other kinds of permissions che ... ... rocess has both a filesystem user ID and an effective user ID. The (Linux-specific) filesystem user ID is used for permissions checking when accessing filesystem objects, while the effective user ID is used for various other kinds of permissions che ... ... lds of the semid_ds structure are as follows: sem_perm This is an ipc_perm structure (see below) that specifies the access permissions on the semaphore set. sem_otime Time of last semop (2) system call. sem_ctime Time of creation of semaphore set or time of ... __seq; /* シーケンス番号 */ }; The least significant 9 bits of the mode field of the ipc_perm structure define the access permissions for the shared memory segment. The permission bits are as follows: 0400 Read by user 0200 Write by user 0040 Read by group ... CNT , GETZCNT , IPC_STAT , SEM_STAT , SEM_STAT_ANY , SETALL , or SETVAL and the calling process does not have the required permissions on the semaphore set and does not have the CAP_IPC_OWNER capability in the user namespace that governs its IPC namespace. ... ... ". On Linux systems with a devpts filesystem (present since Linux 2.2), the kernel normally sets the correct ownership and permissions for the pseudoterminal slave when the master is opened ( posix_openpt (3)), so that nothing must be done by grantpt (). Th ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。