These signals are used to report various errors generated by an operation done by the program. They do not necessarily indicate a programming error in the program, but an error that prevents an operating system call from completing. The default action for all of them is to cause the process to terminate.
SIGPIPE
signal. If SIGPIPE
is blocked, handled or
ignored, the offending call fails with EPIPE
instead.
Pipes and FIFO special files are discussed in more detail in section Pipes and FIFOs.
Another cause of SIGPIPE
is when you try to output to a socket
that isn't connected. See section Sending Data.
In the GNU system, SIGLOST
is generated when any server program
dies unexpectedly. It is usually fine to ignore the signal; whatever
call was made to the server that died just returns an error.
Go to the first, previous, next, last section, table of contents.