JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... amespaces (7). 準拠 getgroups (): SVr4, 4.3BSD, POSIX.1-2001, POSIX.1-2008. setgroups (): SVr4, 4.3BSD. Since setgroups () requires privilege, it is not covered by POSIX.1. 注意 プロセスは、実効グループ ID に加え、最大 NGROUPS_MAX までの補助グループ ID を ... ている。 C ライブラリとカーネルの違い At the kernel level, user IDs and group IDs are a per-thread attribute. However, POSIX requires that all threads in a process share the same credentials. The NPTL threading implementation handles the POSIX requirements ... ... amespaces (7). 準拠 getgroups (): SVr4, 4.3BSD, POSIX.1-2001, POSIX.1-2008. setgroups (): SVr4, 4.3BSD. Since setgroups () requires privilege, it is not covered by POSIX.1. 注意 プロセスは、実効グループ ID に加え、最大 NGROUPS_MAX までの補助グループ ID を ... ている。 C ライブラリとカーネルの違い At the kernel level, user IDs and group IDs are a per-thread attribute. However, POSIX requires that all threads in a process share the same credentials. The NPTL threading implementation handles the POSIX requirements ... ... ath がすでに存在する場合エラーを返す。 RENAME_NOREPLACE can't be employed together with RENAME_EXCHANGE . RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: * ext4 (Linux 3.15); * btrfs ... inux, such as CODA and XFS, is ignored by the kernel's whiteout support code, as of Linux 4.19, at least.) RENAME_WHITEOUT requires the same privileges as creating a device node (i.e., the CAP_MKNOD capability). RENAME_WHITEOUT can't be employed together ... with RENAME_EXCHANGE . RENAME_WHITEOUT requires support from the underlying filesystem. Among the filesystems that provide that support are tmpfs (since Linux 3.18), ext4 ... ... ath がすでに存在する場合エラーを返す。 RENAME_NOREPLACE can't be employed together with RENAME_EXCHANGE . RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: * ext4 (Linux 3.15); * btrfs ... inux, such as CODA and XFS, is ignored by the kernel's whiteout support code, as of Linux 4.19, at least.) RENAME_WHITEOUT requires the same privileges as creating a device node (i.e., the CAP_MKNOD capability). RENAME_WHITEOUT can't be employed together ... with RENAME_EXCHANGE . RENAME_WHITEOUT requires support from the underlying filesystem. Among the filesystems that provide that support are tmpfs (since Linux 3.18), ext4 ... ... ath がすでに存在する場合エラーを返す。 RENAME_NOREPLACE can't be employed together with RENAME_EXCHANGE . RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: * ext4 (Linux 3.15); * btrfs ... inux, such as CODA and XFS, is ignored by the kernel's whiteout support code, as of Linux 4.19, at least.) RENAME_WHITEOUT requires the same privileges as creating a device node (i.e., the CAP_MKNOD capability). RENAME_WHITEOUT can't be employed together ... with RENAME_EXCHANGE . RENAME_WHITEOUT requires support from the underlying filesystem. Among the filesystems that provide that support are tmpfs (since Linux 3.18), ext4 ... ... amespaces (7). 準拠 getgroups (): SVr4, 4.3BSD, POSIX.1-2001, POSIX.1-2008. setgroups (): SVr4, 4.3BSD. Since setgroups () requires privilege, it is not covered by POSIX.1. 注意 プロセスは、実効グループ ID に加え、最大 NGROUPS_MAX までの補助グループ ID を ... ている。 C ライブラリとカーネルの違い At the kernel level, user IDs and group IDs are a per-thread attribute. However, POSIX requires that all threads in a process share the same credentials. The NPTL threading implementation handles the POSIX requirements ... ... amespaces (7). 準拠 getgroups (): SVr4, 4.3BSD, POSIX.1-2001, POSIX.1-2008. setgroups (): SVr4, 4.3BSD. Since setgroups () requires privilege, it is not covered by POSIX.1. 注意 プロセスは、実効グループ ID に加え、最大 NGROUPS_MAX までの補助グループ ID を ... ている。 C ライブラリとカーネルの違い At the kernel level, user IDs and group IDs are a per-thread attribute. However, POSIX requires that all threads in a process share the same credentials. The NPTL threading implementation handles the POSIX requirements ... ... 合、 O_CLOEXEC , O_DIRECTORY , O_NOFOLLOW 以外のフラグビットは無視される。 Opening a file or directory with the O_PATH flag requires no permissions on the object itself (but does require execute permission on the directories in the path prefix). Depending ... on the subsequent operation, a check for suitable file permissions may be performed (e.g., fchdir (2) requires execute permission on the directory referred to by its file descriptor argument). By contrast, obtaining a reference to a ... filesystem object by opening it with the O_RDONLY flag requires that the caller have read permission on the object, even when the subsequent operation (e.g., fchdir (2), fstat (2)) does ... ... 合、 O_CLOEXEC , O_DIRECTORY , O_NOFOLLOW 以外のフラグビットは無視される。 Opening a file or directory with the O_PATH flag requires no permissions on the object itself (but does require execute permission on the directories in the path prefix). Depending ... on the subsequent operation, a check for suitable file permissions may be performed (e.g., fchdir (2) requires execute permission on the directory referred to by its file descriptor argument). By contrast, obtaining a reference to a ... filesystem object by opening it with the O_RDONLY flag requires that the caller have read permission on the object, even when the subsequent operation (e.g., fchdir (2), fstat (2)) does ... ... 合、 O_CLOEXEC , O_DIRECTORY , O_NOFOLLOW 以外のフラグビットは無視される。 Opening a file or directory with the O_PATH flag requires no permissions on the object itself (but does require execute permission on the directories in the path prefix). Depending ... on the subsequent operation, a check for suitable file permissions may be performed (e.g., fchdir (2) requires execute permission on the directory referred to by its file descriptor argument). By contrast, obtaining a reference to a ... filesystem object by opening it with the O_RDONLY flag requires that the caller have read permission on the object, even when the subsequent operation (e.g., fchdir (2), fstat (2)) does ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。