Lines Matching refs:its

97 and @code{raise}) generates its own particular kind of signal.  The
167 that kind of signal. The program specifies its choice using functions
180 its @dfn{default action} takes place. Each kind of signal has its own
186 When a signal terminates a process, its parent process can determine the
393 divisible by four. (Each kind of computer has its own requirements for
620 This signal is sent to a parent process whenever one of its child
689 background job attempts to write to the terminal or set its modes.
766 exceeds its soft resource limit on CPU time. @xref{Limits on Resources}.
805 reformat its display accordingly.
875 prefixes its output with this string. It adds a colon and a space
1147 signal that was delivered is automatically blocked by default before its
1149 @code{sa_mask}. If you want that signal not to be blocked within its
1305 Each signal number has its own set of flags. Each call to
1355 handling of signals from its parent process. However, when you load a
1361 program image.) Of course, the new program can establish its own
1527 Blocking the signal delays its delivery until it is unblocked, once the
1705 /* @r{Find the process that signaled us, and record its status.} */
1714 /* @r{If process has terminated, stop waiting for its output.} */
1831 This function returns its value in a static object, reusing the same
1910 could run ``in the middle of'' an assignment to the variable if its type
2045 protecting its use with another object, perhaps one whose type
2067 This macro evaluates @var{expression} once, and examines its value as
2227 In spite of its name, it can be used for a lot of things other than
2350 changes its real UID as well as its effective UID, you may not have
2361 the receiving process has changed its effective user ID from the
2362 set-user-ID mode bit on its process image file, then the owner of the
2363 process image file is used in place of its current effective user ID.
2382 for the child to complete its initialization. The child process tells
2563 @dfn{signal mask}. Each process has its own signal mask. When you
2564 create a new process (@pxref{Creating a Process}), it inherits its
2572 because each thread has its own signal mask and there is no single process
2614 can't predict what its contents are when your program starts running.)
2694 might confuse it or corrupt its data.
2765 @c its lock.
2923 Please read about its disadvantages, in the following section, before
3181 its action indicates that the signal stack is used, the system arranges
3226 signal handling. When a signal is received by the process and its