JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... tal swap space size */ unsigned long freeswap; /* Swap space still available */ unsigned short procs; /* Number of current processes */ char _f[22]; /* Pads structure to 64 bytes */ }; In the above structure, the sizes of the memory and swap fields are gi ... tal swap space size */ unsigned long freeswap; /* Swap space still available */ unsigned short procs; /* Number of current processes */ unsigned long totalhigh; /* Total high memory size */ unsigned long freehigh; /* Available high memory size */ unsigned ... ... aces have the same content. Memory writes, file mappings ( mmap (2)), and unmappings ( munmap (2)) performed by one of the processes do not affect the other. The child process is an exact duplicate of the parent process except for the following points: * ... ts that may trigger this error: * the RLIMIT_NPROC soft resource limit (set via setrlimit (2)), which limits the number of processes and threads for a real user ID, was reached; * the kernel's system-wide limit on the number of processes and threads, /pro ... ... 5 min %lu\n" "RAM: total %lu / free %lu / shared %lu\n" "Memory in buffers = %lu\nSwap: total %lu / free %lu\n" "Number of processes = %d\n", s_info.uptime, s_info.loads[0], s_info.loads[1], s_info.loads[2], s_info.totalram, s_info.freeram, s_info.sharedr ... : total 15343616 / free 827392 / shared 8237056 Memory in buffers = 5066752 Swap: total 27881472 / free 24698880 Number of processes = 40 関連項目 intro (2), syscall (2), errno (3) この文書について この man ページは Linux man-pages プロジェクトのリリース ... ... ed, at which time it is sent SIGKILL . (This latter point describes Linux behavior. Implementations vary in how they treat processes which continue to consume CPU time after reaching the soft limit. Portable applications that need to catch this signal sho ... file descriptors that an unprivileged process (one without the CAP_SYS_RESOURCE capability) may have "in flight" to other processes, by being passed across UNIX domain sockets. This limit applies to the sendmsg (2) system call. For further details, see u ... ocess (or, more precisely on Linux, threads) for the real user ID of the calling process. So long as the current number of processes belonging to this process's real user ID is greater than or equal to this limit, fork (2) fails with the error EAGAIN . Th ... ... ed, at which time it is sent SIGKILL . (This latter point describes Linux behavior. Implementations vary in how they treat processes which continue to consume CPU time after reaching the soft limit. Portable applications that need to catch this signal sho ... file descriptors that an unprivileged process (one without the CAP_SYS_RESOURCE capability) may have "in flight" to other processes, by being passed across UNIX domain sockets. This limit applies to the sendmsg (2) system call. For further details, see u ... ocess (or, more precisely on Linux, threads) for the real user ID of the calling process. So long as the current number of processes belonging to this process's real user ID is greater than or equal to this limit, fork (2) fails with the error EAGAIN . Th ... ... ed, at which time it is sent SIGKILL . (This latter point describes Linux behavior. Implementations vary in how they treat processes which continue to consume CPU time after reaching the soft limit. Portable applications that need to catch this signal sho ... file descriptors that an unprivileged process (one without the CAP_SYS_RESOURCE capability) may have "in flight" to other processes, by being passed across UNIX domain sockets. This limit applies to the sendmsg (2) system call. For further details, see u ... ocess (or, more precisely on Linux, threads) for the real user ID of the calling process. So long as the current number of processes belonging to this process's real user ID is greater than or equal to this limit, fork (2) fails with the error EAGAIN . Th ... ... ed, at which time it is sent SIGKILL . (This latter point describes Linux behavior. Implementations vary in how they treat processes which continue to consume CPU time after reaching the soft limit. Portable applications that need to catch this signal sho ... file descriptors that an unprivileged process (one without the CAP_SYS_RESOURCE capability) may have "in flight" to other processes, by being passed across UNIX domain sockets. This limit applies to the sendmsg (2) system call. For further details, see u ... ocess (or, more precisely on Linux, threads) for the real user ID of the calling process. So long as the current number of processes belonging to this process's real user ID is greater than or equal to this limit, fork (2) fails with the error EAGAIN . Th ... ... ed, at which time it is sent SIGKILL . (This latter point describes Linux behavior. Implementations vary in how they treat processes which continue to consume CPU time after reaching the soft limit. Portable applications that need to catch this signal sho ... file descriptors that an unprivileged process (one without the CAP_SYS_RESOURCE capability) may have "in flight" to other processes, by being passed across UNIX domain sockets. This limit applies to the sendmsg (2) system call. For further details, see u ... ocess (or, more precisely on Linux, threads) for the real user ID of the calling process. So long as the current number of processes belonging to this process's real user ID is greater than or equal to this limit, fork (2) fails with the error EAGAIN . Th ... ... る。 親プロセスが SA_NOCLDWAIT を設定した場合、 SIGCHLD シグナルが送られるかどうかは定義されていない。 Signals sent to other processes 終了するプロセスがセッションのリーダーで、 そのプロセスの制御端末がそのセッションの制御端末である場合、 この制御端末のフォ ... 送られる。 孤立した (orphaned) プロセスグループの説明は setpgid (2) を参照。 Except in the above cases, where the signalled processes may be children of the terminating process, termination of a process does not in general cause a signal to be sent to chil ... ... ed, at which time it is sent SIGKILL . (This latter point describes Linux behavior. Implementations vary in how they treat processes which continue to consume CPU time after reaching the soft limit. Portable applications that need to catch this signal sho ... file descriptors that an unprivileged process (one without the CAP_SYS_RESOURCE capability) may have "in flight" to other processes, by being passed across UNIX domain sockets. This limit applies to the sendmsg (2) system call. For further details, see u ... ocess (or, more precisely on Linux, threads) for the real user ID of the calling process. So long as the current number of processes belonging to this process's real user ID is greater than or equal to this limit, fork (2) fails with the error EAGAIN . Th ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。