JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... 付けた際に、カーネルは そのシグナルに関する情報を呼び出し者に返す。 これを行う一般的な方法が二つある。 * sigwaitinfo (2), sigtimedwait (2), sigwait (3) は、指定されたシグナル集合のシグナルの一つが配送されるまで実行を中断する。 どのシステムコールや関数で ... synonyms for the same value) on Alpha but SIGLOST on SPARC. リアルタイムシグナル Starting with version 2.2, Linux supports real-time signals as originally defined in the POSIX.1b real-time extensions (and now included in POSIX.1-2001). The range of s ... upported real-time signals is defined by the macros SIGRTMIN and SIGRTMAX . POSIX.1-2001 requires that an implementation support at leas ... ... eated. When nonzero, larger dumps are truncated to this size. RLIMIT_CPU This is a limit, in seconds, on the amount of CPU time that the process can consume. When the process reaches the soft limit, it is sent a SIGXCPU signal. The default action for ... the signal can be caught, and the handler can return control to the main program. If the process continues to consume CPU time, it will be sent SIGXCPU once per second until the hard limit is reached, at which time it is sent SIGKILL . (This latter ... operation, where it sets a maximum on the total bytes in shared memory segments (see shmget (2)) that may be locked by the real user ID of the calling process. The shmctl (2) SHM_LOCK locks are accounted for separately from the per-process memory loc ... ... eated. When nonzero, larger dumps are truncated to this size. RLIMIT_CPU This is a limit, in seconds, on the amount of CPU time that the process can consume. When the process reaches the soft limit, it is sent a SIGXCPU signal. The default action for ... the signal can be caught, and the handler can return control to the main program. If the process continues to consume CPU time, it will be sent SIGXCPU once per second until the hard limit is reached, at which time it is sent SIGKILL . (This latter ... operation, where it sets a maximum on the total bytes in shared memory segments (see shmget (2)) that may be locked by the real user ID of the calling process. The shmctl (2) SHM_LOCK locks are accounted for separately from the per-process memory loc ... ... eated. When nonzero, larger dumps are truncated to this size. RLIMIT_CPU This is a limit, in seconds, on the amount of CPU time that the process can consume. When the process reaches the soft limit, it is sent a SIGXCPU signal. The default action for ... the signal can be caught, and the handler can return control to the main program. If the process continues to consume CPU time, it will be sent SIGXCPU once per second until the hard limit is reached, at which time it is sent SIGKILL . (This latter ... operation, where it sets a maximum on the total bytes in shared memory segments (see shmget (2)) that may be locked by the real user ID of the calling process. The shmctl (2) SHM_LOCK locks are accounted for separately from the per-process memory loc ... ... eated. When nonzero, larger dumps are truncated to this size. RLIMIT_CPU This is a limit, in seconds, on the amount of CPU time that the process can consume. When the process reaches the soft limit, it is sent a SIGXCPU signal. The default action for ... the signal can be caught, and the handler can return control to the main program. If the process continues to consume CPU time, it will be sent SIGXCPU once per second until the hard limit is reached, at which time it is sent SIGKILL . (This latter ... operation, where it sets a maximum on the total bytes in shared memory segments (see shmget (2)) that may be locked by the real user ID of the calling process. The shmctl (2) SHM_LOCK locks are accounted for separately from the per-process memory loc ... ... eated. When nonzero, larger dumps are truncated to this size. RLIMIT_CPU This is a limit, in seconds, on the amount of CPU time that the process can consume. When the process reaches the soft limit, it is sent a SIGXCPU signal. The default action for ... the signal can be caught, and the handler can return control to the main program. If the process continues to consume CPU time, it will be sent SIGXCPU once per second until the hard limit is reached, at which time it is sent SIGKILL . (This latter ... operation, where it sets a maximum on the total bytes in shared memory segments (see shmget (2)) that may be locked by the real user ID of the calling process. The shmctl (2) SHM_LOCK locks are accounted for separately from the per-process memory loc ... ... eated. When nonzero, larger dumps are truncated to this size. RLIMIT_CPU This is a limit, in seconds, on the amount of CPU time that the process can consume. When the process reaches the soft limit, it is sent a SIGXCPU signal. The default action for ... the signal can be caught, and the handler can return control to the main program. If the process continues to consume CPU time, it will be sent SIGXCPU once per second until the hard limit is reached, at which time it is sent SIGKILL . (This latter ... operation, where it sets a maximum on the total bytes in shared memory segments (see shmget (2)) that may be locked by the real user ID of the calling process. The shmctl (2) SHM_LOCK locks are accounted for separately from the per-process memory loc ... ... 行します。 command が終了すると、 time はこのプログラム実行時における、時間に関する統計情報を標準エラー出力に出力します。表示される統計情報は以下の三つから構成さ ... れます: (i) 起動から終了までに経過した実時間 (real time)、(ii) ユーザー CPU 時間 ( times (2) が返す struct tms の tms_utime と tms_cutime 値の合計)、 (iii) システム CPU 時間 ... ( times (2) が返す struct tms の tms_stime と tms_cstime 値の合計)。 ( bash (1) などの) いくつかのシェルには、時間とその他のリソー ... ... value ); int setitimer(int which , const struct itimerval * new_value , struct itimerval * old_value ); 説明 システムは 1 個のプロセスにつき 3 個 ... あるタイマーが満了すると、 プロセスにシグナルが送られ、 タイマーは (0 でなければ) 指定されたインターバルに再設定される。 ITIMER_REAL 実時間 (real time) で減少し、満了すると SIGALRM が送られる。 ITIMER_VIRTUAL プロセスが実行されている間のみ減少し、満 ... tv_sec; /* seconds */ suseconds_t tv_usec; /* microseconds */ }; getitimer () 関数は、 which で指定されたタイマー ( ITIMER_REAL , ITIMER_VIRTUAL , ITIMER_PROF のどれか) の現在の値 (すなわち、次のタイマー満了までの残り時間) を、 curr_value で指定された ... ... value ); int setitimer(int which , const struct itimerval * new_value , struct itimerval * old_value ); 説明 システムは 1 個のプロセスにつき 3 個 ... あるタイマーが満了すると、 プロセスにシグナルが送られ、 タイマーは (0 でなければ) 指定されたインターバルに再設定される。 ITIMER_REAL 実時間 (real time) で減少し、満了すると SIGALRM が送られる。 ITIMER_VIRTUAL プロセスが実行されている間のみ減少し、満 ... tv_sec; /* seconds */ suseconds_t tv_usec; /* microseconds */ }; getitimer () 関数は、 which で指定されたタイマー ( ITIMER_REAL , ITIMER_VIRTUAL , ITIMER_PROF のどれか) の現在の値 (すなわち、次のタイマー満了までの残り時間) を、 curr_value で指定された ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。