Lines Matching refs:always

216 always by the names defined here.  This is because the number for a
499 It cannot be handled or ignored, and is therefore always fatal.  It is
506 it a @code{SIGKILL} signal will almost always cause it to go away.
589 On @gnusystems{} @code{SIGIO} will always be generated properly
640 This signal is special---it always makes the process continue if it is
643 @code{SIGCONT} always makes the process continue regardless.
700 always causes termination of the process and can't be blocked, handled
701 or ignored.  You can ignore @code{SIGCONT}, but it always causes the
1201 To avoid having problems as a result, always use @code{sigaction} to
1837 function that returns information in the same object, or if it always
1841 fixed object, always reusing the same object in this fashion, and all of
1843 always mention this behavior.
1929 types that are always accessed atomically; you can carefully arrange
1993 these machines, the handler will always print two zeros or two ones.
1999 use a particular data type for which access is always atomic:
2004 The type @code{sig_atomic_t} is always an integer data type, but which
2010 This is an integer data type.  Objects of this type are always accessed
2026 tested and cleared by the main program from time to time, is always safe
2114 after a partial transfer cannot happen on such devices; they always
2492 You must always initialize the signal set with one of these two
2505 defined signals.  It always returns @code{0}.
2948 Primitives}), this has no effect on @code{pause}; it always fails when a
3056 The function @code{sigsuspend} always restores the previous signal mask