<?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: Script / inetd in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433687#M4031</link>
    <description>You may want to add a entry in /etc/inittab so that it gets spawned if one isn't running already</description>
    <pubDate>Mon, 31 Jul 2000 17:19:44 GMT</pubDate>
    <dc:creator>Vikas Khator</dc:creator>
    <dc:date>2000-07-31T17:19:44Z</dc:date>
    <item>
      <title>Script / inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433683#M4027</link>
      <description>I want to check and see if inetd is running every hour.  If not running start inetd.&lt;BR /&gt;&lt;BR /&gt;This is what I have so far.&lt;BR /&gt;&lt;BR /&gt;inedtrunning=$(ps -ef | grep inetd | grep /usr&lt;BR /&gt;&lt;BR /&gt;if [[ -n ${inetdrunning} ]]&lt;BR /&gt;  then&lt;BR /&gt;      ---------------------&lt;BR /&gt;  else&lt;BR /&gt;      ---------------------&lt;BR /&gt;fi&lt;BR /&gt;unset inetdrunning&lt;BR /&gt;&lt;BR /&gt;Thanks, for all help in advance</description>
      <pubDate>Mon, 31 Jul 2000 13:24:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433683#M4027</guid>
      <dc:creator>Junior C.</dc:creator>
      <dc:date>2000-07-31T13:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: Script / inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433684#M4028</link>
      <description>To cut out a grep:-&lt;BR /&gt;&lt;BR /&gt;inetdrunning=$(ps -e|grep inetd)&lt;BR /&gt;&lt;BR /&gt;if [[ -n ${inetdrunning ]];&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;I must confess however that I have never had a server where inetd died. I would be looking to HP to cure the problem if that was the case.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;John</description>
      <pubDate>Mon, 31 Jul 2000 13:34:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433684#M4028</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2000-07-31T13:34:34Z</dc:date>
    </item>
    <item>
      <title>Re: Script / inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433685#M4029</link>
      <description>Junior:&lt;BR /&gt;&lt;BR /&gt;OOPS! Forgot the closing tick mark:&lt;BR /&gt;&lt;BR /&gt;if (( `ps -ef|grep $WHAT|grep -c -v "grep $WHAT"` &amp;gt; 0 )) &lt;BR /&gt; &lt;BR /&gt;...JRF...</description>
      <pubDate>Mon, 31 Jul 2000 13:47:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433685#M4029</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2000-07-31T13:47:03Z</dc:date>
    </item>
    <item>
      <title>Re: Script / inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433686#M4030</link>
      <description>Junior:&lt;BR /&gt;&lt;BR /&gt;I'm not sure why you are worried that the superdaemon is/isn't running as it seems you would have/detect lots of problems if it wasn't.&lt;BR /&gt;&lt;BR /&gt;However, one general way to test if a particular process is running is to do the following:&lt;BR /&gt;&lt;BR /&gt;WHAT=inetd&lt;BR /&gt;if (( `ps -ef|grep $WHAT|grep -c -v "grep $WHAT" &amp;gt; 0 ))&lt;BR /&gt;then&lt;BR /&gt;echo "$WHAT running"&lt;BR /&gt;else&lt;BR /&gt;echo "$WHAT not running"&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Mon, 31 Jul 2000 13:47:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433686#M4030</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2000-07-31T13:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: Script / inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433687#M4031</link>
      <description>You may want to add a entry in /etc/inittab so that it gets spawned if one isn't running already</description>
      <pubDate>Mon, 31 Jul 2000 17:19:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433687#M4031</guid>
      <dc:creator>Vikas Khator</dc:creator>
      <dc:date>2000-07-31T17:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: Script / inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433688#M4032</link>
      <description>As has been mentioned here, inetd doesn't die.  Look at what inetd has been patched for.  You'll find that it hangs, blocks, loops out of control, issues timeouts, doesn't behave well under a heavy load, etc.  Your method of checking for the process running will not catch any of these.  And they happen often enough that HP has issued a patch for them.  And the list doesn't include dieing unexpectedly, but that could be what the next patch is issued for.&lt;BR /&gt;&lt;BR /&gt;I'd suggest using a method that will verify that inetd is acutally working.  Such as running, telnet $(hostname) 13, which will return the system time.  Although, you'll have to devise a method for testing.  ie I don't know of a broken inetd that you can test against for error messages.  Can a hung inetd be stopped and restarted? etc.&lt;BR /&gt;&lt;BR /&gt;Using such a method will not only catch inetd not running, but other error conditions also.</description>
      <pubDate>Tue, 01 Aug 2000 16:48:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/script-inetd/m-p/2433688#M4032</guid>
      <dc:creator>curt larson</dc:creator>
      <dc:date>2000-08-01T16:48:35Z</dc:date>
    </item>
  </channel>
</rss>

