<?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 Run Levels in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115289#M446881</link>
    <description>Hi:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; In my aim script I shoulf set the PATH variable and that fixed all the problem....&lt;BR /&gt;&lt;BR /&gt;If you had started with the '/sbin/init.d/template', or looked at it more closely, you might have seen :-) that it declares a minimal PATH:&lt;BR /&gt;&lt;BR /&gt;PATH=/usr/sbin:/usr/bin:/sbin&lt;BR /&gt;&lt;BR /&gt;Too, when you test startup and shutdown (kill) scripts at a commandline, and they work, but then fail when executed in the '/sbin/rc?.d' sequence during changes in 'init' level, you can immediately begin to suspect deficiencies in your running environment.  Aside from the PATH, you must include any environmental variable that you need.  This is the reason I suggested that you test first at the command line in your normal shell environment.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 24 Jun 2008 10:54:26 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2008-06-24T10:54:26Z</dc:date>
    <item>
      <title>Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115256#M446848</link>
      <description>Hi guys,&lt;BR /&gt;&lt;BR /&gt;During installation I will have to install a service.&lt;BR /&gt;1. Can you give me a quick overview about the run-levels on HPUX 11.23 PARisc?&lt;BR /&gt;2. How do I create the S/K links on /sbin/rcX.d? is there any command for that, as the chkconfig on linux or create a soft link via "ln"?&lt;BR /&gt;3. Do you have a good HP documentation link for this subject?&lt;BR /&gt;&lt;BR /&gt;tx.</description>
      <pubDate>Mon, 23 Jun 2008 06:57:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115256#M446848</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T06:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115257#M446849</link>
      <description>Have a look at:&lt;BR /&gt;&lt;A href="http://forums12.itrc.hp.com/service/forums/questionanswer.do?&amp;amp;threadId=1042729" target="_blank"&gt;http://forums12.itrc.hp.com/service/forums/questionanswer.do?&amp;amp;threadId=1042729&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B9106-90008/init.1M.html" target="_blank"&gt;http://docs.hp.com/en/B9106-90008/init.1M.html&lt;/A&gt;</description>
      <pubDate>Mon, 23 Jun 2008 07:01:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115257#M446849</guid>
      <dc:creator>Venkatesh BL</dc:creator>
      <dc:date>2008-06-23T07:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115258#M446850</link>
      <description>hi;&lt;BR /&gt;&lt;BR /&gt;read the man page.&lt;BR /&gt;# man rc&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;mustafa</description>
      <pubDate>Mon, 23 Jun 2008 07:13:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115258#M446850</guid>
      <dc:creator>Mustafa Gulercan</dc:creator>
      <dc:date>2008-06-23T07:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115259#M446851</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;run level directories contains scripts that will run while start up, while changing run levels ( up or down) or shutting down. While going down from rc3 to rc1 K scripts run, while going up from s1 to s3 S scripts run. S is for starting, K is for killing.&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/ director is your directory where you'll put your script for start and kill. And the synax is below:&lt;BR /&gt;&lt;BR /&gt;&lt;SERVICE_SCRIPT_NAME&gt; &lt;BR /&gt;&lt;BR /&gt;#!/sbin/sh&lt;BR /&gt;&lt;BR /&gt;case "$1" in&lt;BR /&gt;start_msg)&lt;BR /&gt;echo "Start &lt;YOUR_SERVICE&gt;"&lt;BR /&gt;;;&lt;BR /&gt;&lt;BR /&gt;stop_msg)&lt;BR /&gt;echo "Stop &lt;YOUR_SERVICE&gt;"&lt;BR /&gt;;;&lt;BR /&gt;&lt;BR /&gt;'start')&lt;BR /&gt;&lt;COMMAND_TO_START_SERVICE&gt;&lt;BR /&gt;;;&lt;BR /&gt;'stop')&lt;BR /&gt;# Stop the oracle databases&lt;BR /&gt;&lt;COMMAND_TO_STOP_SERVICE&gt;&lt;BR /&gt;;;&lt;BR /&gt;esac&lt;BR /&gt;&lt;BR /&gt;and after you should create links for Rc directories. change &lt;SERVICE_NAME&gt; with appropriate file names. And also you may change run levels in which the service will be started and killed.&lt;BR /&gt;&lt;BR /&gt;ln -s /sbin/init.d/&lt;SERVICE_SCRIPT_NAME&gt; /sbin/rc3.d/S999&lt;SERVICE_NAME&gt;&lt;BR /&gt;&lt;BR /&gt;ln -s /sbin/init.d/&lt;SERVICE_SCRIPT_NAME&gt;  /sbin/rc3.d/K999&lt;SERVICE_NAME&gt;&lt;BR /&gt;&lt;BR /&gt;Kenan.&lt;BR /&gt;&lt;/SERVICE_NAME&gt;&lt;/SERVICE_SCRIPT_NAME&gt;&lt;/SERVICE_NAME&gt;&lt;/SERVICE_SCRIPT_NAME&gt;&lt;/SERVICE_NAME&gt;&lt;/COMMAND_TO_STOP_SERVICE&gt;&lt;/COMMAND_TO_START_SERVICE&gt;&lt;/YOUR_SERVICE&gt;&lt;/YOUR_SERVICE&gt;&lt;/SERVICE_SCRIPT_NAME&gt;</description>
      <pubDate>Mon, 23 Jun 2008 07:16:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115259#M446851</guid>
      <dc:creator>Kenan Erdey</dc:creator>
      <dc:date>2008-06-23T07:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115260#M446852</link>
      <description>&amp;gt;Kenan: And also you may change run levels in which the service will be started and killed.&lt;BR /&gt;ln -s ... /sbin/rc3.d/S999&lt;SERVICE_NAME&gt;&lt;BR /&gt;ln -s ... /sbin/rc3.d/K999&lt;SERVICE_NAME&gt;&lt;BR /&gt;&lt;BR /&gt;Typically these numbers add to 1000, so that they are done in reverse order.&lt;BR /&gt;&lt;BR /&gt;&lt;/SERVICE_NAME&gt;&lt;/SERVICE_NAME&gt;</description>
      <pubDate>Mon, 23 Jun 2008 07:48:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115260#M446852</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-06-23T07:48:57Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115261#M446853</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;I wonder about those numbers... (Knnn/Snnn)&lt;BR /&gt;As I saw and also as dennis said, these number will complete to 1000.&lt;BR /&gt;For all the UNIX I know, the complition it to 100.&lt;BR /&gt;&lt;BR /&gt;so,&lt;BR /&gt;1. are the lower number reserved for something?&lt;BR /&gt;2. what is the reason for these higer number?&lt;BR /&gt;3. if I have a service that for all the other UNIXes started at 91 and killed on 09 - what numbers you suggest me to set?&lt;BR /&gt;&lt;BR /&gt;tx</description>
      <pubDate>Mon, 23 Jun 2008 09:11:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115261#M446853</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T09:11:59Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115262#M446854</link>
      <description>and another important questions&lt;BR /&gt;1. if my service uses networking - basically I can start it on level 2 - don't I?&lt;BR /&gt;2. it this acceptable to do so?&lt;BR /&gt;3. I saw that most of the sevices/daemons don't have a kill script on level 0 - what should happen on system shutdown? (should I put K links on level 0, 1?&lt;BR /&gt;&lt;BR /&gt;tx again</description>
      <pubDate>Mon, 23 Jun 2008 09:15:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115262#M446854</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T09:15:51Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115263#M446855</link>
      <description>&amp;gt;1. are the lower number reserved for something?&lt;BR /&gt;&lt;BR /&gt;No, except they are done first.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;2. what is the reason for these higher number?&lt;BR /&gt;&lt;BR /&gt;The range from 000 to 999?  For more choices.&lt;BR /&gt;Note these numbers are an illusion.  The scripts are done in ascii order and the reverse.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;3. if I have a service that for all the other UNIXes started at 91 and killed on 09 - what numbers you suggest me to set?&lt;BR /&gt;&lt;BR /&gt;Probably 901 and 009.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;1. if my service uses networking - basically I can start it on level 2 - don't I?&lt;BR /&gt;&lt;BR /&gt;You have to order it after the networking starts.</description>
      <pubDate>Mon, 23 Jun 2008 09:29:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115263#M446855</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-06-23T09:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115264#M446856</link>
      <description>what about level 0 and 1?&lt;BR /&gt;should I put K link there?</description>
      <pubDate>Mon, 23 Jun 2008 10:03:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115264#M446856</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T10:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115265#M446857</link>
      <description>one more:&lt;BR /&gt;&lt;BR /&gt;What about the fact that when I reboot the machine I don't see my product in the printed down list:&lt;BR /&gt;XXX daemon was stopped.........OK&lt;BR /&gt;bla bla is down................OK&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;should I do something specific in order to get in this list?&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jun 2008 10:11:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115265#M446857</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T10:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115266#M446858</link>
      <description>&amp;gt;what about level 0 and 1?  should I put K link there?&lt;BR /&gt;&lt;BR /&gt;rc(1M) says that S is at rcN.d and K is at rcN-1.d.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;What about the fact that when I reboot the machine I don't see my product in the printed down list: should I do something specific in order to get in this list?&lt;BR /&gt;&lt;BR /&gt;Do you have start_msg &amp;amp; stop_msg entry as Kenan mentions?</description>
      <pubDate>Mon, 23 Jun 2008 10:41:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115266#M446858</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-06-23T10:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115267#M446859</link>
      <description>&amp;gt;Do you have start_msg &amp;amp; stop_msg entry as Kenan mentions?&lt;BR /&gt;&lt;BR /&gt;I don't use these names? should I? I have functions "stop" and "start"...&lt;BR /&gt;&lt;BR /&gt;by the way.&lt;BR /&gt;I didn't understant the issue with init script:&lt;BR /&gt;If I want my service to be started for level 3 and above and be down for level 2 and below, where should I put my links? because somehow, when I'm on level 3 and I moved to level 4 with "init 4" the system runs my S link from rc4.d and fails.&lt;BR /&gt;shouldn't it recognize the the service is already up? should I remove the S link from rc4.d?&lt;BR /&gt;&lt;BR /&gt;tx&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jun 2008 11:03:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115267#M446859</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T11:03:55Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115268#M446860</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;The manpages for 'rc(1M)' and the original 10.0 whitepaper on system startup scripts (which *still* applies today) provide a complete overview of the requirements you should meet.&lt;BR /&gt;&lt;BR /&gt;The "rule of 1000" as mentioned, the difference betweent the number assigned to a start script and a kill script is discussed.&lt;BR /&gt;&lt;BR /&gt;Use '/sbin/init.d/template' as a starting model for any script you write.  In this way, you will follow the essential rules noted in the documentation.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/934/startup.pdf" target="_blank"&gt;http://docs.hp.com/en/934/startup.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-60130/rc.1M.html" target="_blank"&gt;http://docs.hp.com/en/B2355-60130/rc.1M.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jun 2008 11:06:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115268#M446860</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2008-06-23T11:06:20Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115269#M446861</link>
      <description>1. I can go with this template but am I required to?&lt;BR /&gt;I already have a file that works on all the other platform. Can I make it work with minimal changes?&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jun 2008 12:19:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115269#M446861</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T12:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115270#M446862</link>
      <description>Hi (again):&lt;BR /&gt;&lt;BR /&gt;&amp;gt; I can go with this template but am I required to?  I already have a file that works on all the other platform. Can I make it work with minimal changes?&lt;BR /&gt;&lt;BR /&gt;You are *not* required to use the template, but you *are* required to follow the same logic.  This logic is also discussed in the aforementioned documentation I cited.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Mon, 23 Jun 2008 12:28:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115270#M446862</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2008-06-23T12:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115271#M446863</link>
      <description>of course same logic!!!&lt;BR /&gt;&lt;BR /&gt;but,&lt;BR /&gt;will it be acceptable to use a script that doesn't have "stop_message" and "start_message" for example (and "start_proc" instead "start")&lt;BR /&gt;&lt;BR /&gt;do I have to use the rc.config.d/xxx file?&lt;BR /&gt;&lt;BR /&gt;tx</description>
      <pubDate>Mon, 23 Jun 2008 12:51:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115271#M446863</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T12:51:48Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115272#M446864</link>
      <description>Hi (again):&lt;BR /&gt;&lt;BR /&gt;&amp;gt; but, will it be acceptable to use a script that doesn't have "stop_message" and "start_message" for example (and "start_proc" instead "start")&lt;BR /&gt;&lt;BR /&gt;NO.  You need to look at the documentation and the 'template' logic.  These requirements are clearly documented.  If you want your script to participate in startup and shutdown in HP-UX then follow the HP-UX guidelines!&lt;BR /&gt;&lt;BR /&gt;You are making this much more difficult than it needs to be.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; do I have to use the rc.config.d/xxx file?&lt;BR /&gt;&lt;BR /&gt;This is somewhat optional.  However, by declaring variables in a file in '/etc/rc.config.d/' you can easily disable your startup and shutdown script without having to unlink the 'sbin/rc?.d' files from the '/sbin/init.d/' script.  Look at '/etc/rc.config.d/mailservs' and '/sbin/init.d/sendmail' for one example of this mechanism.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jun 2008 13:30:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115272#M446864</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2008-06-23T13:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115273#M446865</link>
      <description>ok man,&lt;BR /&gt;I understand that.&lt;BR /&gt;&lt;BR /&gt;let me give you the following scenario:&lt;BR /&gt;I have script on /sbin/init.d&lt;BR /&gt;S link on rc3&lt;BR /&gt;K link on rc2&lt;BR /&gt;&lt;BR /&gt;If I run /sbin/init.d/my_s start twice, in the second time, I failed with the msg that the service is alreay up.&lt;BR /&gt;&lt;BR /&gt;BUT,&lt;BR /&gt;if I move from level 3 to level 2 (the service is still up), and if I move from level 2 to 3, the sys tries to start the service again and it gets error msg from service - but not from the script as I expected.&lt;BR /&gt;How can I avoid that?&lt;BR /&gt;Why the script doesn't avoid this case?&lt;BR /&gt;&lt;BR /&gt;tx&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jun 2008 14:04:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115273#M446865</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T14:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115274#M446866</link>
      <description>Hi (again):&lt;BR /&gt;&lt;BR /&gt;&amp;gt; If I run /sbin/init.d/my_s start twice, in the second time, I failed with the msg that the service is alreay up.&lt;BR /&gt;&lt;BR /&gt;Yes, that would be expected.  You have done nothing to stop (kill) the first instance.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; BUT, if I move from level 3 to level 2 (the service is still up), and if I move from level 2 to 3, the sys tries to start the service again and it gets error msg from service - but not from the script as I expected.&lt;BR /&gt;&lt;BR /&gt;Then your shutdown ("K"ill) script failed to stop the first instance of your process.&lt;BR /&gt;&lt;BR /&gt;There are any number of good examples if you look at the scripts in the '/sbin/init.d' directory.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jun 2008 14:18:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115274#M446866</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2008-06-23T14:18:34Z</dc:date>
    </item>
    <item>
      <title>Re: Init Run Levels</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115275#M446867</link>
      <description>Hi dude,&lt;BR /&gt;&lt;BR /&gt;In my script, before starting it, I check that the service is yet up!&lt;BR /&gt;if it's up, I print the msg that the service is alreay started.&lt;BR /&gt;According to documentation (if I got it right) when I have S script on level 3 and K script on level 2, when I move from level 3 to 2, the Kill script on rc2.d shouldn't be invoked (only the K scripts from level 3)&lt;BR /&gt;that's why the service is still up when I moved from 3 to 2.&lt;BR /&gt;you understand my problem here?&lt;BR /&gt;&lt;BR /&gt;also, I will look at more examples, but if you have some enlighment I will be happy to hear.&lt;BR /&gt;&lt;BR /&gt;tx</description>
      <pubDate>Mon, 23 Jun 2008 14:49:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/init-run-levels/m-p/5115275#M446867</guid>
      <dc:creator>devshlom</dc:creator>
      <dc:date>2008-06-23T14:49:24Z</dc:date>
    </item>
  </channel>
</rss>

