<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>probe::signal.send.return</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="SystemTap Tapset Reference Manual"><link rel="up" href="signal.stp.html" title="Chapter 17. Signal Tapset"><link rel="prev" href="API-signal-send.html" title="probe::signal.send"><link rel="next" href="API-signal-send-sig-queue.html" title="probe::signal.send_sig_queue"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span class="phrase">probe::signal.send.return</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="API-signal-send.html">Prev</a> </td><th width="60%" align="center">Chapter 17. Signal Tapset</th><td width="20%" align="right"> <a accesskey="n" href="API-signal-send-sig-queue.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="API-signal-send-return"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>probe::signal.send.return — Signal being sent to a process completed (deprecated in SystemTap 2.1) </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><pre class="synopsis">signal.send.return </pre></div><div class="refsect1"><a name="idp147747668"></a><h2>Values</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="parameter"><code>retstr</code></em></span></dt><dd><p> The return value to either __group_send_sig_info, specific_send_sig_info, or send_sigqueue </p></dd><dt><span class="term"><em class="parameter"><code>send2queue</code></em></span></dt><dd><p> Indicates whether the sent signal was sent to an existing sigqueue </p></dd><dt><span class="term"><em class="parameter"><code>name</code></em></span></dt><dd><p> The name of the function used to send out the signal </p></dd><dt><span class="term"><em class="parameter"><code>shared</code></em></span></dt><dd><p> Indicates whether the sent signal is shared by the thread group. </p></dd></dl></div></div><div class="refsect1"><a name="idp147752548"></a><h2>Context</h2><p> The signal's sender. (correct?) </p></div><div class="refsect1"><a name="idp147753188"></a><h2>Description</h2><p> Possible __group_send_sig_info and specific_send_sig_info return values are as follows; </p><p> 0 -- The signal is successfully sent to a process, which means that, (1) the signal was ignored by the receiving process, (2) this is a non-RT signal and the system already has one queued, and (3) the signal was successfully added to the sigqueue of the receiving process. </p><p> -EAGAIN -- The sigqueue of the receiving process is overflowing, the signal was RT, and the signal was sent by a user using something other than <code class="function">kill</code>. </p><p> Possible send_group_sigqueue and send_sigqueue return values are as follows; </p><p> 0 -- The signal was either successfully added into the sigqueue of the receiving process, or a SI_TIMER entry is already queued (in which case, the overrun count will be simply incremented). </p><p> 1 -- The signal was ignored by the receiving process. </p><p> -1 -- (send_sigqueue only) The task was marked exiting, allowing * posix_timer_event to redirect it to the group leader. </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="API-signal-send.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="signal.stp.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="API-signal-send-sig-queue.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span class="phrase">probe::signal.send</span> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> <span class="phrase">probe::signal.send_sig_queue</span></td></tr></table></div></body></html>