blob: 7fddcaaf7bcb8ce7e645ae6a61b134ff1cb3c612 [file] [log] [blame]
<html lang="en">
<head>
<title>Operation Error Signals - The GNU C Library</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="The GNU C Library">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Standard-Signals.html#Standard-Signals" title="Standard Signals">
<link rel="prev" href="Job-Control-Signals.html#Job-Control-Signals" title="Job Control Signals">
<link rel="next" href="Miscellaneous-Signals.html#Miscellaneous-Signals" title="Miscellaneous Signals">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
This file documents the GNU C library.
This is Edition 0.12, last updated 2007-10-27,
of `The GNU C Library Reference Manual', for version
2.8 (Sourcery G++ Lite 2011.03-41).
Copyright (C) 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2001, 2002,
2003, 2007, 2008, 2010 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with the
Invariant Sections being ``Free Software Needs Free Documentation''
and ``GNU Lesser General Public License'', the Front-Cover texts being
``A GNU Manual'', and with the Back-Cover Texts as in (a) below. A
copy of the license is included in the section entitled "GNU Free
Documentation License".
(a) The FSF's Back-Cover Text is: ``You have the freedom to
copy and modify this GNU manual. Buying copies from the FSF
supports it in developing GNU and promoting software freedom.''-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
--></style>
<link rel="stylesheet" type="text/css" href="../cs.css">
</head>
<body>
<div class="node">
<a name="Operation-Error-Signals"></a>
<p>
Next:&nbsp;<a rel="next" accesskey="n" href="Miscellaneous-Signals.html#Miscellaneous-Signals">Miscellaneous Signals</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="Job-Control-Signals.html#Job-Control-Signals">Job Control Signals</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Standard-Signals.html#Standard-Signals">Standard Signals</a>
<hr>
</div>
<h4 class="subsection">24.2.6 Operation Error Signals</h4>
<p>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.
<!-- signal.h -->
<!-- POSIX.1 -->
<div class="defun">
&mdash; Macro: int <b>SIGPIPE</b><var><a name="index-SIGPIPE-2887"></a></var><br>
<blockquote><p><a name="index-pipe-signal-2888"></a><a name="index-broken-pipe-signal-2889"></a>Broken pipe. If you use pipes or FIFOs, you have to design your
application so that one process opens the pipe for reading before
another starts writing. If the reading process never starts, or
terminates unexpectedly, writing to the pipe or FIFO raises a
<code>SIGPIPE</code> signal. If <code>SIGPIPE</code> is blocked, handled or
ignored, the offending call fails with <code>EPIPE</code> instead.
<p>Pipes and FIFO special files are discussed in more detail in <a href="Pipes-and-FIFOs.html#Pipes-and-FIFOs">Pipes and FIFOs</a>.
<p>Another cause of <code>SIGPIPE</code> is when you try to output to a socket
that isn't connected. See <a href="Sending-Data.html#Sending-Data">Sending Data</a>.
</p></blockquote></div>
<!-- signal.h -->
<!-- GNU -->
<div class="defun">
&mdash; Macro: int <b>SIGLOST</b><var><a name="index-SIGLOST-2890"></a></var><br>
<blockquote><p><a name="index-lost-resource-signal-2891"></a>Resource lost. This signal is generated when you have an advisory lock
on an NFS file, and the NFS server reboots and forgets about your lock.
<p>In the GNU system, <code>SIGLOST</code> 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.
</p></blockquote></div>
<!-- signal.h -->
<!-- BSD -->
<div class="defun">
&mdash; Macro: int <b>SIGXCPU</b><var><a name="index-SIGXCPU-2892"></a></var><br>
<blockquote><p>CPU time limit exceeded. This signal is generated when the process
exceeds its soft resource limit on CPU time. See <a href="Limits-on-Resources.html#Limits-on-Resources">Limits on Resources</a>.
</p></blockquote></div>
<!-- signal.h -->
<!-- BSD -->
<div class="defun">
&mdash; Macro: int <b>SIGXFSZ</b><var><a name="index-SIGXFSZ-2893"></a></var><br>
<blockquote><p>File size limit exceeded. This signal is generated when the process
attempts to extend a file so it exceeds the process's soft resource
limit on file size. See <a href="Limits-on-Resources.html#Limits-on-Resources">Limits on Resources</a>.
</p></blockquote></div>
</body></html>