<?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: Monitoring inetd in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457836#M716545</link>
    <description>the problem is what i have to write in the SERVICE_CMD! Qhat command does start inetd? I don't think i can put init in SERVICE_CMD raw!</description>
    <pubDate>Wed, 25 Oct 2000 16:08:41 GMT</pubDate>
    <dc:creator>Roberto Volsa</dc:creator>
    <dc:date>2000-10-25T16:08:41Z</dc:date>
    <item>
      <title>Monitoring inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457833#M716542</link>
      <description>The objective is create a package which monitors inetd; but inetd is a socket and it only listen: a process born only if a remote request reach the server. Thus: which processes have i to monitor and write down on the configuration files of the package?</description>
      <pubDate>Wed, 25 Oct 2000 15:46:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457833#M716542</guid>
      <dc:creator>Roberto Volsa</dc:creator>
      <dc:date>2000-10-25T15:46:56Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457834#M716543</link>
      <description>inetd will log contact requests, etc. to the files specified in etc/inetd.conf</description>
      <pubDate>Wed, 25 Oct 2000 15:55:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457834#M716543</guid>
      <dc:creator>Alan Riggs</dc:creator>
      <dc:date>2000-10-25T15:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457835#M716544</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;I'm not sure exactly what you want.  the inetd daemon will be visible to 'ps' if you want to make sure its running.&lt;BR /&gt;&lt;BR /&gt;You can start inetd with connection logging enabled.  The default is not to do so.  See "man inetd" for more information.  Hopefully this information helps you.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 25 Oct 2000 15:58:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457835#M716544</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2000-10-25T15:58:40Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457836#M716545</link>
      <description>the problem is what i have to write in the SERVICE_CMD! Qhat command does start inetd? I don't think i can put init in SERVICE_CMD raw!</description>
      <pubDate>Wed, 25 Oct 2000 16:08:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457836#M716545</guid>
      <dc:creator>Roberto Volsa</dc:creator>
      <dc:date>2000-10-25T16:08:41Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457837#M716546</link>
      <description>Do I understand that you want a serviceguard package to swap inetd back and forth between primary and failover hosts?&lt;BR /&gt;&lt;BR /&gt;Why?&lt;BR /&gt;&lt;BR /&gt;Inetd should run independently on each box.  It is necessary for basic networking functionality.</description>
      <pubDate>Wed, 25 Oct 2000 16:32:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457837#M716546</guid>
      <dc:creator>Alan Riggs</dc:creator>
      <dc:date>2000-10-25T16:32:27Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457838#M716547</link>
      <description>inetd is started at startup (run level 2 and higher) by the script /sbin/rc2.d/S500inetd with the start parameter.&lt;BR /&gt;&lt;BR /&gt;You can configure your setup so that if inetd dies - it gets restarted:&lt;BR /&gt;&lt;BR /&gt;INETDRUNNING=`ps -ef | grep -c [i]netd`&lt;BR /&gt;if [ ! $INETDRUNNING ]&lt;BR /&gt;then&lt;BR /&gt;/sbin/rc2.d/S500inetd start&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Good luck</description>
      <pubDate>Wed, 25 Oct 2000 16:32:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457838#M716547</guid>
      <dc:creator>Kofi ARTHIABAH</dc:creator>
      <dc:date>2000-10-25T16:32:59Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457839#M716548</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;As Alan asked, are you talking about MC/ServiceGuard 'packages'?  If so, I agree with him, inetd is not something that you want to start/stop/reconfigure in a failover.  A similar thread on this issue can be found here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0x726168c57f64d4118fee0090279cd0f9,00.html" target="_blank"&gt;http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0x726168c57f64d4118fee0090279cd0f9,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Does this help?&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 25 Oct 2000 16:47:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457839#M716548</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2000-10-25T16:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring inetd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457840#M716549</link>
      <description>Yes, the package has to monitor inetd process; the package is used for load balancing purposes and each package with different ips let the customer know where messages aresent.&lt;BR /&gt;Roberto</description>
      <pubDate>Thu, 26 Oct 2000 07:32:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-inetd/m-p/2457840#M716549</guid>
      <dc:creator>Roberto Volsa</dc:creator>
      <dc:date>2000-10-26T07:32:36Z</dc:date>
    </item>
  </channel>
</rss>

