<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic signal not delivered in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/signal-not-delivered/m-p/3878369#M98943</link>
    <description>I write a C program.&lt;BR /&gt;I set a signal handler for SIGTERM with sigaction. sigaction returns ok, everything seems fine.&lt;BR /&gt;A moment later, when the program is in a sleep(), I send a SIGTERM to the process. And the problem : the signal is not delivered, the process does not interrupt its sleep().&lt;BR /&gt;Has anyone encountered this problem. Why is my signal sometimes yes and sometimes not delivered ?</description>
    <pubDate>Wed, 11 Oct 2006 09:44:56 GMT</pubDate>
    <dc:creator>Dubost_2</dc:creator>
    <dc:date>2006-10-11T09:44:56Z</dc:date>
    <item>
      <title>signal not delivered</title>
      <link>https://community.hpe.com/t5/operating-system-linux/signal-not-delivered/m-p/3878369#M98943</link>
      <description>I write a C program.&lt;BR /&gt;I set a signal handler for SIGTERM with sigaction. sigaction returns ok, everything seems fine.&lt;BR /&gt;A moment later, when the program is in a sleep(), I send a SIGTERM to the process. And the problem : the signal is not delivered, the process does not interrupt its sleep().&lt;BR /&gt;Has anyone encountered this problem. Why is my signal sometimes yes and sometimes not delivered ?</description>
      <pubDate>Wed, 11 Oct 2006 09:44:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/signal-not-delivered/m-p/3878369#M98943</guid>
      <dc:creator>Dubost_2</dc:creator>
      <dc:date>2006-10-11T09:44:56Z</dc:date>
    </item>
    <item>
      <title>Re: signal not delivered</title>
      <link>https://community.hpe.com/t5/operating-system-linux/signal-not-delivered/m-p/3878370#M98944</link>
      <description>Hi,&lt;BR /&gt;by design.&lt;BR /&gt;&lt;BR /&gt;From man 3C sleep&lt;BR /&gt;"If a SIGALRM is generated for a multi-threaded process, it may not be delivered to a thread currently in sleep(). See sigwait(2) man page for details. In a multi-threaded process delivery of a SIGALRM to a&lt;BR /&gt;thread in sleep() simply causes sleep() to return without invoking the SIGALRM handler."&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Oct 2006 09:59:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/signal-not-delivered/m-p/3878370#M98944</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-10-11T09:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: signal not delivered</title>
      <link>https://community.hpe.com/t5/operating-system-linux/signal-not-delivered/m-p/3878371#M98945</link>
      <description>Hi,&lt;BR /&gt;Thank you for your answer.&lt;BR /&gt;This man page is not applicable.&lt;BR /&gt;My process is mono-threaded and I try to deliver the signal SIGTERM, not SIGALRM.&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Oct 2006 10:05:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/signal-not-delivered/m-p/3878371#M98945</guid>
      <dc:creator>Dubost_2</dc:creator>
      <dc:date>2006-10-11T10:05:47Z</dc:date>
    </item>
  </channel>
</rss>

