<?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 Reserved SIGNAL for application in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/reserved-signal-for-application/m-p/3423667#M71235</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There are 2 reserved signals for application namely SIGUSR1 and SIGUSR2.&lt;BR /&gt;&lt;BR /&gt;In my application i already have used these 2 reserved signals. now, i have an requiremnt to send one more notication to application using signal. How can i acheive this.&lt;BR /&gt;&lt;BR /&gt;I have used SIGUSR1 to pause, SIGUSR2 to resume. I need to sent one more signal to check table values in database.&lt;BR /&gt;&lt;BR /&gt;How can i send this custom signal as both SIGUSR1 and SIGUSR2 are already occupied.&lt;BR /&gt;&lt;BR /&gt;Many Thanks</description>
    <pubDate>Wed, 17 Nov 2004 01:38:02 GMT</pubDate>
    <dc:creator>Lalit Seth</dc:creator>
    <dc:date>2004-11-17T01:38:02Z</dc:date>
    <item>
      <title>Reserved SIGNAL for application</title>
      <link>https://community.hpe.com/t5/operating-system-linux/reserved-signal-for-application/m-p/3423667#M71235</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There are 2 reserved signals for application namely SIGUSR1 and SIGUSR2.&lt;BR /&gt;&lt;BR /&gt;In my application i already have used these 2 reserved signals. now, i have an requiremnt to send one more notication to application using signal. How can i acheive this.&lt;BR /&gt;&lt;BR /&gt;I have used SIGUSR1 to pause, SIGUSR2 to resume. I need to sent one more signal to check table values in database.&lt;BR /&gt;&lt;BR /&gt;How can i send this custom signal as both SIGUSR1 and SIGUSR2 are already occupied.&lt;BR /&gt;&lt;BR /&gt;Many Thanks</description>
      <pubDate>Wed, 17 Nov 2004 01:38:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/reserved-signal-for-application/m-p/3423667#M71235</guid>
      <dc:creator>Lalit Seth</dc:creator>
      <dc:date>2004-11-17T01:38:02Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved SIGNAL for application</title>
      <link>https://community.hpe.com/t5/operating-system-linux/reserved-signal-for-application/m-p/3423668#M71236</link>
      <description>Perhaps you could use SIGTSTP and SIGCONT&lt;BR /&gt;for your existing pause/resume feature.&lt;BR /&gt;I believe SIGTSTP is the signal sent by&lt;BR /&gt;the shell when when you type Control-Z, and&lt;BR /&gt;SIGCONT is the signal sent when you do an&lt;BR /&gt;"fg" or "bg" to resume.  If your app doesn't&lt;BR /&gt;interact with the shell or otherwise need&lt;BR /&gt;SIGTSTP or SIGCONT then I think it's safe to&lt;BR /&gt;re-use them.&lt;BR /&gt;</description>
      <pubDate>Wed, 17 Nov 2004 13:02:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/reserved-signal-for-application/m-p/3423668#M71236</guid>
      <dc:creator>Gregory Fruth</dc:creator>
      <dc:date>2004-11-17T13:02:14Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved SIGNAL for application</title>
      <link>https://community.hpe.com/t5/operating-system-linux/reserved-signal-for-application/m-p/3423669#M71237</link>
      <description>The other thing is that you can trap *ANY* signal (except for SIGKILL) and do whatever you want on it.&lt;BR /&gt;&lt;BR /&gt;For instance, if it's a daemon, you could use 'SIGHUP' (which in daemons is usually used to re-read configuration files etc.), or 'SIGINT' (same as hitting ctrl-c, interrupt) or any other of which doesn't do something you want it too.</description>
      <pubDate>Wed, 17 Nov 2004 18:43:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/reserved-signal-for-application/m-p/3423669#M71237</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-11-17T18:43:38Z</dc:date>
    </item>
  </channel>
</rss>

