<?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 Re: /bin/sh scripts: process still alive when the father die. in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/bin-sh-scripts-process-still-alive-when-the-father-die/m-p/3073887#M808906</link>
    <description>Thanks really a lot. It works fine with the 'nohup' instruction.</description>
    <pubDate>Thu, 18 Sep 2003 08:38:54 GMT</pubDate>
    <dc:creator>bernard bedetti</dc:creator>
    <dc:date>2003-09-18T08:38:54Z</dc:date>
    <item>
      <title>/bin/sh scripts: process still alive when the father die.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bin-sh-scripts-process-still-alive-when-the-father-die/m-p/3073885#M808904</link>
      <description>I'd like to know if it is possible that a script 'X' (which contains a loop with a sleep) launched from another script 'Y', remains alive when the script 'Y' die ?&lt;BR /&gt; 1. I think I have to use the trap instruction, but I don't know exactly how.&lt;BR /&gt; 2. Could be another solution ?&lt;BR /&gt;I hope I'm clear enough !</description>
      <pubDate>Thu, 18 Sep 2003 07:09:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bin-sh-scripts-process-still-alive-when-the-father-die/m-p/3073885#M808904</guid>
      <dc:creator>bernard bedetti</dc:creator>
      <dc:date>2003-09-18T07:09:02Z</dc:date>
    </item>
    <item>
      <title>Re: /bin/sh scripts: process still alive when the father die.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bin-sh-scripts-process-still-alive-when-the-father-die/m-p/3073886#M808905</link>
      <description>Two things I can think of here.&lt;BR /&gt;&lt;BR /&gt;Probably the most sensible thing is to run script X using the "nohup" command.&lt;BR /&gt;&lt;BR /&gt;If you want to trap signals in a script, choose your signal "kill -l" will list the possible signals and do a &lt;BR /&gt;&lt;BR /&gt;trap "" 2 for example.&lt;BR /&gt;&lt;BR /&gt;I think SIGQUIT is the one you are after but signals get sent to all processes in a process group so you would have to trap pretty much everything for all the possible signals that might have killed the parent.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 18 Sep 2003 07:16:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bin-sh-scripts-process-still-alive-when-the-father-die/m-p/3073886#M808905</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2003-09-18T07:16:33Z</dc:date>
    </item>
    <item>
      <title>Re: /bin/sh scripts: process still alive when the father die.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bin-sh-scripts-process-still-alive-when-the-father-die/m-p/3073887#M808906</link>
      <description>Thanks really a lot. It works fine with the 'nohup' instruction.</description>
      <pubDate>Thu, 18 Sep 2003 08:38:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bin-sh-scripts-process-still-alive-when-the-father-die/m-p/3073887#M808906</guid>
      <dc:creator>bernard bedetti</dc:creator>
      <dc:date>2003-09-18T08:38:54Z</dc:date>
    </item>
  </channel>
</rss>

