JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... する。 説明 これらの関数は 10 の x 乗の値を返す。 Note well : These functions perform exactly the same task as the functions described in exp10 (3), with the difference that the latter functions are now standardized in TS 18661-4:2015. Those latter function ... s should be used in preference to the functions described in this page. バージョン These functions first appeared in glibc in version 2.1. Since glibc 2.27, the use of these functi ... ... する。 説明 これらの関数は 10 の x 乗の値を返す。 Note well : These functions perform exactly the same task as the functions described in exp10 (3), with the difference that the latter functions are now standardized in TS 18661-4:2015. Those latter function ... s should be used in preference to the functions described in this page. バージョン These functions first appeared in glibc in version 2.1. Since glibc 2.27, the use of these functi ... ... する。 説明 これらの関数は 10 の x 乗の値を返す。 Note well : These functions perform exactly the same task as the functions described in exp10 (3), with the difference that the latter functions are now standardized in TS 18661-4:2015. Those latter function ... s should be used in preference to the functions described in this page. バージョン These functions first appeared in glibc in version 2.1. Since glibc 2.27, the use of these functi ... ... の場合はそうである。 C ライブラリとカーネルの違い On Linux, the kernel provides a getcwd () system call, which the functions described in this page will use if possible. The system call takes the same arguments as the library function of the same name, but ... urrent directory into another mount namespace. When dealing with pathname from untrusted sources, callers of the functions described in this page should consider checking whether the returned pathname starts with '/' or '(' to avoid misinterpreting an unr ... eachable path as a relative pathname. バグ Since the Linux 2.6.36 change that added "(unreachable)" in the circumstances described above, the glibc implementation of getcwd () has failed to conform to POSIX and returned a relative pathname when the API ... ... の場合はそうである。 C ライブラリとカーネルの違い On Linux, the kernel provides a getcwd () system call, which the functions described in this page will use if possible. The system call takes the same arguments as the library function of the same name, but ... urrent directory into another mount namespace. When dealing with pathname from untrusted sources, callers of the functions described in this page should consider checking whether the returned pathname starts with '/' or '(' to avoid misinterpreting an unr ... eachable path as a relative pathname. バグ Since the Linux 2.6.36 change that added "(unreachable)" in the circumstances described above, the glibc implementation of getcwd () has failed to conform to POSIX and returned a relative pathname when the API ... ... の場合はそうである。 C ライブラリとカーネルの違い On Linux, the kernel provides a getcwd () system call, which the functions described in this page will use if possible. The system call takes the same arguments as the library function of the same name, but ... urrent directory into another mount namespace. When dealing with pathname from untrusted sources, callers of the functions described in this page should consider checking whether the returned pathname starts with '/' or '(' to avoid misinterpreting an unr ... eachable path as a relative pathname. バグ Since the Linux 2.6.36 change that added "(unreachable)" in the circumstances described above, the glibc implementation of getcwd () has failed to conform to POSIX and returned a relative pathname when the API ... ... の場合はそうである。 C ライブラリとカーネルの違い On Linux, the kernel provides a getcwd () system call, which the functions described in this page will use if possible. The system call takes the same arguments as the library function of the same name, but ... urrent directory into another mount namespace. When dealing with pathname from untrusted sources, callers of the functions described in this page should consider checking whether the returned pathname starts with '/' or '(' to avoid misinterpreting an unr ... eachable path as a relative pathname. バグ Since the Linux 2.6.36 change that added "(unreachable)" in the circumstances described above, the glibc implementation of getcwd () has failed to conform to POSIX and returned a relative pathname when the API ... ... 成できる inotify インスタンス数の上限のチェック時 ( inotify (7) 参照) Modifying process user and group IDs Subject to rules described in the relevant manual pages, a process can use the following APIs to modify its user and group IDs: setuid (2) ( setgid ( ... em user (group) ID. Changes to a process's effective user or group ID can also affect the process "dumpable" attribute, as described in prctl (2). Changes to process user and group IDs can affect the capabilities of the process, as described in capabiliti ... / グループ ID は Linux による拡張である。 注意 Various fields in the /proc/[pid]/status file show the process credentials described above. See proc (5) for further information. POSIX のスレッド仕様では、これらの識別子がプロセス内の全スレッドで 共有される ... ... s , unsigned int flags ); 説明 If fd is opened for writing, the vmsplice () system call maps nr_segs ranges of user memory described by iov into a pipe. If fd is opened for reading, the vmsplice () system call fills nr_segs ranges of user memory described ... ... ed, in which case the dumpable flag may instead be reset to the value in /proc/sys/fs/suid_dumpable , in the circumstances described under PR_SET_DUMPABLE in prctl (2). Note that changes to the "dumpable" attribute may cause ownership of files in the proc ... ess's /proc/[pid] directory to change to root:root , as described in proc (5). * prctl (2) の PR_SET_KEEPCAPS フラグはクリアされる。 * (Linux 2.4.36 以降 / 2.6.23 以降) set-user-ID や set- ... , but it exists (with some variations) on other UNIX systems. 注意 One sometimes sees execve () (and the related functions described in exec (3)) described as "executing a new process" (or similar). This is a highly misleading description: there is no new ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。