JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... ime was not sufficing for the needs of Linux. Often, this library was referred to (ambiguously) as just "libc". Linux libc released major versions 2, 3, 4, and 5, as well as many minor versions of those releases. Linux libc4 was the last version to use t ... Linux distributions. However, notwithstanding the original motivations of the Linux libc effort, by the time glibc 2.0 was released (in 1997), it was clearly superior to Linux libc, and all major Linux distributions that had been using Linux libc soon sw ... ... ime was not sufficing for the needs of Linux. Often, this library was referred to (ambiguously) as just "libc". Linux libc released major versions 2, 3, 4, and 5, as well as many minor versions of those releases. Linux libc4 was the last version to use t ... Linux distributions. However, notwithstanding the original motivations of the Linux libc effort, by the time glibc 2.0 was released (in 1997), it was clearly superior to Linux libc, and all major Linux distributions that had been using Linux libc soon sw ... ... アルタイム拡張について記載している。 POSIX.1-1996 POSIX.1 の 1996 年の改訂版。 POSIX.1b と POSIX.1c を取り込んでいる。 XPG3 Released in 1989, this was the first release of the X/Open Portability Guide to be based on a POSIX standard (POSIX.1-1988). This m ... volume guide was developed by the X/Open Group, a multivendor consortium. XPG4 A revision of the X/Open Portability Guide, released in 1992. This revision incorporated POSIX.2. XPG4v2 XPG4 の 1994年改訂版。 Spec 1170 とも呼ばれる。 1170 とはこの標準規格が ... ... ead_detach () should be called for each thread that an application creates, so that system resources for the thread can be released. (But note that the resources of any threads for which one of these actions has not been done will be freed when the proce ... ... the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Released under the GNU General Public License version 2 or later. 関連項目 script (1), scriptreplay (1) 入手方法 この scriptlive コ ... ... uently use waitpid (2) (or similar) to learn the termination status of the child; at that point the zombie process slot is released. SIGCHLD シグナルのサポートが実装されている場合、 このシグナルは親プロセスに送られる。 親プロセスが SA_NOCLDWAIT を設定した ... ... the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Released under the GNU General Public License version 2 or later. 関連項目 script (1), scriptlive (1) 入手方法 この scriptreplay コ ... ... not guaranteed. Any unwritten dirty pages will not be freed. If the application wishes to ensure that dirty pages will be released, it should call fsync (2) or fdatasync (2) first. 返り値 成功した場合は 0 が返される。 失敗した場合はエラー番号が返される。 ... ... not guaranteed. Any unwritten dirty pages will not be freed. If the application wishes to ensure that dirty pages will be released, it should call fsync (2) or fdatasync (2) first. 返り値 成功した場合は 0 が返される。 失敗した場合はエラー番号が返される。 ... ... not guaranteed. Any unwritten dirty pages will not be freed. If the application wishes to ensure that dirty pages will be released, it should call fsync (2) or fdatasync (2) first. 返り値 成功した場合は 0 が返される。 失敗した場合はエラー番号が返される。 ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。