<?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: Bypass startup script in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379962#M197352</link>
    <description>one method would be to edit the scripts.&lt;BR /&gt;&lt;BR /&gt;one trick is to create a temp file (lock) file in /tmp when the script started sucessful.&lt;BR /&gt;&lt;BR /&gt;change application start-up script (level 3) to create:&lt;BR /&gt;/tmp/application.lev3&lt;BR /&gt;&lt;BR /&gt;change application script that starts in the next level, say (level 5).  have this script check on if file /tmp/applicaiton.lev3 is present.  if present, then continue with script, if NOT-present, exit.&lt;BR /&gt;&lt;BR /&gt;sounds like some coding work..&lt;BR /&gt;&lt;BR /&gt;another method, is to combine all your scripts into one large script.. this might be real easy to maintain.. maybe put all your scripting in a file in Leve6 (user defined services).</description>
    <pubDate>Wed, 15 Sep 2004 23:01:00 GMT</pubDate>
    <dc:creator>D Block 2</dc:creator>
    <dc:date>2004-09-15T23:01:00Z</dc:date>
    <item>
      <title>Bypass startup script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379960#M197350</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Anyone knows any workaround to bypass an application start-up script stored in level 4 ? example i have 5 start-up scripts, script 1 and 2 executed fine but script 3 was not and this failure prevent script 4 and 5 from starting, anyway we can timeout the script 3 failure ?&lt;BR /&gt;&lt;BR /&gt;Please help. Thanks:)</description>
      <pubDate>Wed, 15 Sep 2004 20:44:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379960#M197350</guid>
      <dc:creator>Lee Huei</dc:creator>
      <dc:date>2004-09-15T20:44:13Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass startup script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379961#M197351</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;This is on hp-ux machine ( hp-ux 11.00). Thanks.</description>
      <pubDate>Wed, 15 Sep 2004 21:16:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379961#M197351</guid>
      <dc:creator>Lee Huei</dc:creator>
      <dc:date>2004-09-15T21:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass startup script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379962#M197352</link>
      <description>one method would be to edit the scripts.&lt;BR /&gt;&lt;BR /&gt;one trick is to create a temp file (lock) file in /tmp when the script started sucessful.&lt;BR /&gt;&lt;BR /&gt;change application start-up script (level 3) to create:&lt;BR /&gt;/tmp/application.lev3&lt;BR /&gt;&lt;BR /&gt;change application script that starts in the next level, say (level 5).  have this script check on if file /tmp/applicaiton.lev3 is present.  if present, then continue with script, if NOT-present, exit.&lt;BR /&gt;&lt;BR /&gt;sounds like some coding work..&lt;BR /&gt;&lt;BR /&gt;another method, is to combine all your scripts into one large script.. this might be real easy to maintain.. maybe put all your scripting in a file in Leve6 (user defined services).</description>
      <pubDate>Wed, 15 Sep 2004 23:01:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379962#M197352</guid>
      <dc:creator>D Block 2</dc:creator>
      <dc:date>2004-09-15T23:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass startup script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379963#M197353</link>
      <description>If hp-ux means,&lt;BR /&gt;&lt;BR /&gt; what is the message's get you on /etc/rc.log file. It contains all informations and failures of startup script's&lt;BR /&gt;&lt;BR /&gt; I am not sure that, lower conventional scripts make the next coming scripts not to execute there. Try to check permission ( execution ) of script3 and try to run it as,&lt;BR /&gt;&lt;BR /&gt; set -x ( debugging mode ) on the start of script there.&lt;BR /&gt;&lt;BR /&gt; Before testing it on startup, try to test on shell itself one time with debugging there.&lt;BR /&gt;&lt;BR /&gt; And more, if you are creating startup script, try to put one variable that control's the script to start or not execute on /etc/rc.config.d/scriptname&lt;BR /&gt;&lt;BR /&gt; See other script's contents there.</description>
      <pubDate>Thu, 16 Sep 2004 01:43:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379963#M197353</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2004-09-16T01:43:23Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass startup script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379964#M197354</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Thanks for replying. The scripts are application scripts. Is there anything like time-out the failed script so that the subsequent startup script wont be affected?&lt;BR /&gt;&lt;BR /&gt;Thanks:)</description>
      <pubDate>Thu, 16 Sep 2004 01:51:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379964#M197354</guid>
      <dc:creator>Lee Huei</dc:creator>
      <dc:date>2004-09-16T01:51:00Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass startup script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379965#M197355</link>
      <description>Hi,Mico&lt;BR /&gt;&lt;BR /&gt;for cutting the starting scripts is used to press CTRL+ |(pipe)keys simultaneously.&lt;BR /&gt;During a script is waiting for a long time,&lt;BR /&gt;I use the keys in my case.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 16 Sep 2004 02:40:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379965#M197355</guid>
      <dc:creator>KCS_1</dc:creator>
      <dc:date>2004-09-16T02:40:07Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass startup script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379966#M197356</link>
      <description>Oh..sorry,,&lt;BR /&gt;&lt;BR /&gt;I meant NOT bypass,,just cutting the scripts. ;(</description>
      <pubDate>Thu, 16 Sep 2004 02:41:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379966#M197356</guid>
      <dc:creator>KCS_1</dc:creator>
      <dc:date>2004-09-16T02:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass startup script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379967#M197357</link>
      <description>Thanks.  Yeap, i need to know how to bypass.&lt;BR /&gt;&lt;BR /&gt;I know i can terminate the script hung during startup with the ctl+pipe+shift. But this means to terminate the startup.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Sep 2004 02:44:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379967#M197357</guid>
      <dc:creator>Lee Huei</dc:creator>
      <dc:date>2004-09-16T02:44:46Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass startup script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379968#M197358</link>
      <description>To make the timeout on not-running startup scripts, we are not having any specification's there.&lt;BR /&gt;&lt;BR /&gt;But we may manage as,&lt;BR /&gt;&lt;BR /&gt; Make a script which will execute all the correspoding service startup scripts in that.&lt;BR /&gt;So that the script has the control to make the startup timeout on ir-responding scripts there.&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; As like,&lt;BR /&gt;&lt;BR /&gt; /etc/rc4.d/&lt;BR /&gt; script4&lt;BR /&gt;&lt;BR /&gt; which will execute the the scripts on that particular level of startup. But IT is good to keep the standard there. It will be executed based on the fileextenstion so that, in the script also maintain the same ordering there.&lt;BR /&gt;&lt;BR /&gt; Check weather the script is made startup, else timeout. This can be done by executing that script in background and collect the pid of that one, and  check ps and make not to start after that.&lt;BR /&gt;&lt;BR /&gt;AND MORE, I did not try this. I suggest you to try with a simple script which start's 3 service at first and ... go on.&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Sep 2004 03:10:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bypass-startup-script/m-p/3379968#M197358</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2004-09-16T03:10:14Z</dc:date>
    </item>
  </channel>
</rss>

