<?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: init script problem during bootup in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/init-script-problem-during-bootup/m-p/3289273#M181803</link>
    <description>The first p-lace to start is /etc/rc.log which is the log for all startup scripts. Even if you miss any error messages during bootup, they will be found in rc.log. nohup isn't necessary since sshd is a correctly written daemon (it moves itself out of the current session and assigns itself to init). The easiest way to see if sshd is actually started is to add this to the beginning of the script:&lt;BR /&gt; &lt;BR /&gt;set -x&lt;BR /&gt; &lt;BR /&gt;All the debug details will be in /etc/rc.log (and the shutdown steps are appended to rc.log and written to rc.log.old)</description>
    <pubDate>Thu, 27 May 2004 19:49:23 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2004-05-27T19:49:23Z</dc:date>
    <item>
      <title>init script problem during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-script-problem-during-bootup/m-p/3289270#M181800</link>
      <description>HP-UX 11.11&lt;BR /&gt;&lt;BR /&gt;I created init script to start ssh daemon from a template in /sbin/init.d and created /etc/config.d/ file with configuration and added proper links to start it in runlevel 3,which is default for my system.&lt;BR /&gt;&lt;BR /&gt;When I run script by hand from console,ie: /sbin/init.d/sshd start it starts ok.When i do init 2 and then init 3 script also runs ok. But during boot it doesn`t start daemon,although script is executed.I inserted commands like echo "running script..." &amp;gt; /tmp/log and echo "script ran..." &amp;gt;&amp;gt; /tmp/log. It seems like sshd dies...&lt;BR /&gt;&lt;BR /&gt;I searched this forum and found simular problems.I will try with nohup option and some other tips.(but: sshd when started from console goes into backgorund automatically...)&lt;BR /&gt;&lt;BR /&gt;Also,i tried to create 2nd script,which runs oracle with help off dbstart script.Same effect,so it doesn`t look like sshd problem.&lt;BR /&gt;&lt;BR /&gt;Can anyone describe this situation cleanly? I want to understand what is the difference between boot process,when switching to 3rd runlevel and manual command init 3 when in runlevel 2 ? Why daemon can`t start?</description>
      <pubDate>Thu, 27 May 2004 16:03:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-script-problem-during-bootup/m-p/3289270#M181800</guid>
      <dc:creator>someman</dc:creator>
      <dc:date>2004-05-27T16:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: init script problem during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-script-problem-during-bootup/m-p/3289271#M181801</link>
      <description>I have a question :&lt;BR /&gt;&lt;BR /&gt;while the system is starting up, executing rcX.d/Sxxx scripts where you see the pass/fail status screens, do you see your init script being processed ? If yes, is it exiting with "OK" status ?&lt;BR /&gt;&lt;BR /&gt;If the answer to all of the above is YES, then if I were you I would put some sort of a checking mechanism at the end of my init script like&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;/opt/ssh/sbin/sshd&lt;BR /&gt;sleep 5&lt;BR /&gt;ps -ef | grep sshd | grep -v grep &amp;gt;/tmp/dump&lt;BR /&gt;result=`echo $?`&lt;BR /&gt;if [ $result -ne 0 ]&lt;BR /&gt;then&lt;BR /&gt;# either set EXITSTATUS to nonzero for this script and finish execution&lt;BR /&gt;# or retry starting it again&lt;BR /&gt;# upto you&lt;BR /&gt;fi&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;exit $EXITSTATUS&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 27 May 2004 18:09:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-script-problem-during-bootup/m-p/3289271#M181801</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2004-05-27T18:09:08Z</dc:date>
    </item>
    <item>
      <title>Re: init script problem during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-script-problem-during-bootup/m-p/3289272#M181802</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;For ssh I suggest you consider running HP's version of it.  It is avalable from a link at &lt;BR /&gt;&lt;A href="http://www.hp.com/products1/unix/operating/security/index.html#network" target="_blank"&gt;http://www.hp.com/products1/unix/operating/security/index.html#network&lt;/A&gt;&lt;BR /&gt;Be sure to get the Strong Random Number Generator also from a link on that page.&lt;BR /&gt;Here's the direct link for ssh&lt;BR /&gt;&lt;A href="http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=T1471AA" target="_blank"&gt;http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=T1471AA&lt;/A&gt;&lt;BR /&gt;The HP depot for ssh will install init scripts.&lt;BR /&gt;&lt;BR /&gt;I realize this won't answer your question regarding init scirpts, but it will address your ssh problem.  You may get some ideas from looking at the scripts that HP provides.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Tom</description>
      <pubDate>Thu, 27 May 2004 19:05:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-script-problem-during-bootup/m-p/3289272#M181802</guid>
      <dc:creator>Tom Ward_1</dc:creator>
      <dc:date>2004-05-27T19:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: init script problem during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-script-problem-during-bootup/m-p/3289273#M181803</link>
      <description>The first p-lace to start is /etc/rc.log which is the log for all startup scripts. Even if you miss any error messages during bootup, they will be found in rc.log. nohup isn't necessary since sshd is a correctly written daemon (it moves itself out of the current session and assigns itself to init). The easiest way to see if sshd is actually started is to add this to the beginning of the script:&lt;BR /&gt; &lt;BR /&gt;set -x&lt;BR /&gt; &lt;BR /&gt;All the debug details will be in /etc/rc.log (and the shutdown steps are appended to rc.log and written to rc.log.old)</description>
      <pubDate>Thu, 27 May 2004 19:49:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-script-problem-during-bootup/m-p/3289273#M181803</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2004-05-27T19:49:23Z</dc:date>
    </item>
  </channel>
</rss>

