<?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 rc3.d shell in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/rc3-d-shell/m-p/4144875#M725213</link>
    <description>Hello&lt;BR /&gt;I have created startup shell (S99Start) in /sbin/rc3.d.&lt;BR /&gt;This shell simply calls another shell like below.&lt;BR /&gt;sh -c "$AGENTWORKS_DIR/CACustomise/uni_start.sh $1" &amp;gt; /dev/null 2&amp;gt;&amp;amp;1&lt;BR /&gt;&lt;BR /&gt;exit 0&lt;BR /&gt;&lt;BR /&gt;The called shell (uni_start.sh) is always terminated whenever rc3.d shell is finished.&lt;BR /&gt;&lt;BR /&gt;Is this working as design?&lt;BR /&gt;And how can I avoid it?&lt;BR /&gt;(I can only think of nohup currently)&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
    <pubDate>Thu, 14 Feb 2008 08:50:55 GMT</pubDate>
    <dc:creator>?? ??_39</dc:creator>
    <dc:date>2008-02-14T08:50:55Z</dc:date>
    <item>
      <title>rc3.d shell</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rc3-d-shell/m-p/4144875#M725213</link>
      <description>Hello&lt;BR /&gt;I have created startup shell (S99Start) in /sbin/rc3.d.&lt;BR /&gt;This shell simply calls another shell like below.&lt;BR /&gt;sh -c "$AGENTWORKS_DIR/CACustomise/uni_start.sh $1" &amp;gt; /dev/null 2&amp;gt;&amp;amp;1&lt;BR /&gt;&lt;BR /&gt;exit 0&lt;BR /&gt;&lt;BR /&gt;The called shell (uni_start.sh) is always terminated whenever rc3.d shell is finished.&lt;BR /&gt;&lt;BR /&gt;Is this working as design?&lt;BR /&gt;And how can I avoid it?&lt;BR /&gt;(I can only think of nohup currently)&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Feb 2008 08:50:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rc3-d-shell/m-p/4144875#M725213</guid>
      <dc:creator>?? ??_39</dc:creator>
      <dc:date>2008-02-14T08:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: rc3.d shell</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rc3-d-shell/m-p/4144876#M725214</link>
      <description>sh -c "$AGENTWORKS_DIR/CACustomise/uni_start.sh $1" &amp;gt; /dev/null 2&amp;gt;&amp;amp;1&lt;BR /&gt;&lt;BR /&gt;Why are you doing "sh -c"?  Why not just invoke the command:&lt;BR /&gt;$AGENTWORKS_DIR/CACustomise/uni_start.sh $1 ...&lt;BR /&gt;&lt;BR /&gt;&amp;gt;The called shell (uni_start.sh) is always terminated whenever rc3.d shell is finished.&lt;BR /&gt;&lt;BR /&gt;I assume you put uni_start.sh in the background?&lt;BR /&gt;&lt;BR /&gt;&amp;gt;(I can only think of nohup currently)&lt;BR /&gt;&lt;BR /&gt;There is that or you can demonize your process.&lt;BR /&gt;&lt;A href="http://www.ddj.com/architect/184404033" target="_blank"&gt;http://www.ddj.com/architect/184404033&lt;/A&gt;</description>
      <pubDate>Thu, 14 Feb 2008 09:49:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rc3-d-shell/m-p/4144876#M725214</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-02-14T09:49:04Z</dc:date>
    </item>
    <item>
      <title>Re: rc3.d shell</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rc3-d-shell/m-p/4144877#M725215</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Suggest:&lt;BR /&gt;$AGENTWORKS_DIR/CACustomise/uni_start.sh $1" &lt;BR /&gt;&lt;BR /&gt;Become&lt;BR /&gt;&lt;BR /&gt;${AGENTWORKS_DIR}/CACustomise/uni_start.sh ${1}" &lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 14 Feb 2008 10:21:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rc3-d-shell/m-p/4144877#M725215</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-02-14T10:21:18Z</dc:date>
    </item>
    <item>
      <title>Re: rc3.d shell</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rc3-d-shell/m-p/4144878#M725216</link>
      <description>Actually, if coded as above (not nohup, no &amp;amp;), the calling shell (S99....) is waiting for the called shell (uni_start.sh) to finish before it procedes.&lt;BR /&gt;&lt;BR /&gt;my guess is its working as you want to, even tho the "sh -c" is superfluous.&lt;BR /&gt;&lt;BR /&gt;You would need to examine uni_start.sh to see what it starts and if it/they are all running.&lt;BR /&gt;&lt;BR /&gt;fwiw: start / stop scripts should be S(or K) followed by 3 digits, with the numbers adding to 1000 so the correct start / stop order is preserved</description>
      <pubDate>Fri, 15 Feb 2008 19:23:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rc3-d-shell/m-p/4144878#M725216</guid>
      <dc:creator>OldSchool</dc:creator>
      <dc:date>2008-02-15T19:23:50Z</dc:date>
    </item>
  </channel>
</rss>

