<?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: inetd issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022688#M130855</link>
    <description>Hi,&lt;BR /&gt;i think of this problem like a problem with oracle listener (of which i have experience).&lt;BR /&gt;&lt;BR /&gt;Sorry, but in this case there is no solution as far as i know. When you plan such configuration, you should also check that there is no overlay in the configurations.&lt;BR /&gt;&lt;BR /&gt;In oracle listener we can use a single program, listening to both port and with different parameters, or we can use a single port with multiple parameters.&lt;BR /&gt;&lt;BR /&gt;Is it also possible for your program ?&lt;BR /&gt;May bet there are someadvanced settigns, try asking to the software house.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;   Massimo&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 15 Jul 2003 06:00:09 GMT</pubDate>
    <dc:creator>Massimo Bianchi</dc:creator>
    <dc:date>2003-07-15T06:00:09Z</dc:date>
    <item>
      <title>inetd issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022684#M130851</link>
      <description>Hello,&lt;BR /&gt;I have two servers in cluster and two programs that run one on each server and listening to port 94. Well, each program (package) has it's own IP, so there is no problem when both of them are running on the same server because the binding to the port is done by IP, and if they have differnt IPs so there is no problem that they will listen to the same port number, but I need entry in the inetd.conf, and it's the problem because then I'll have two different entries for the same port, how can I solve this issue and tell OS that even it's the same port it's for the different IPs?&lt;BR /&gt;&lt;BR /&gt;thanx.</description>
      <pubDate>Mon, 14 Jul 2003 10:57:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022684#M130851</guid>
      <dc:creator>Alex Lavrov</dc:creator>
      <dc:date>2003-07-14T10:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: inetd issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022685#M130852</link>
      <description>Sockets are only identifiers to system files and need no other special administration since each IP/socket/port will work from the same set network daemon processes.&lt;BR /&gt;&lt;BR /&gt;It will be unnecessary to make duplicate entries in either /etc/inetd.conf or /etc/services.&lt;BR /&gt;&lt;BR /&gt;I thinking that you're thinking too far down in the OSI 7 layer stack since sockets begin at layer four and above making them unique identifiers through the merging of IP and PORT numbers.&lt;BR /&gt;&lt;BR /&gt;Here is a link to 'lsof'.  Use the command 'lsof -i tcp:21' to get a better picture of what open files and processes are using each port.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://hpux.cict.fr/hppd/hpux/Sysadmin/lsof-4.64/" target="_blank"&gt;http://hpux.cict.fr/hppd/hpux/Sysadmin/lsof-4.64/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I'm a huge believer in 'lsof' being apart of every sys admin's tool box for its an extremely useful tool.&lt;BR /&gt;&lt;BR /&gt;Good luck.</description>
      <pubDate>Mon, 14 Jul 2003 11:42:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022685#M130852</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-07-14T11:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: inetd issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022686#M130853</link>
      <description>Alex,&lt;BR /&gt;&lt;BR /&gt;I don't completly understand you question. But I think you want to create a restriction in you inetd.sec file for you server. I think when you invoke a restriction in inetd.sec it will automaticly be used for both ip's because the inetd will work for both ip's and will use the same restrictions for them.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;D.</description>
      <pubDate>Mon, 14 Jul 2003 11:44:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022686#M130853</guid>
      <dc:creator>Dagmar Boelen</dc:creator>
      <dc:date>2003-07-14T11:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: inetd issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022687#M130854</link>
      <description>Well, that's correct, but I want them to run with different parameters, so it can't be the same line in inetd.conf for both services, it should be different, now what can I do?&lt;BR /&gt;&lt;BR /&gt;thanx</description>
      <pubDate>Tue, 15 Jul 2003 05:37:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022687#M130854</guid>
      <dc:creator>Alex Lavrov</dc:creator>
      <dc:date>2003-07-15T05:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: inetd issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022688#M130855</link>
      <description>Hi,&lt;BR /&gt;i think of this problem like a problem with oracle listener (of which i have experience).&lt;BR /&gt;&lt;BR /&gt;Sorry, but in this case there is no solution as far as i know. When you plan such configuration, you should also check that there is no overlay in the configurations.&lt;BR /&gt;&lt;BR /&gt;In oracle listener we can use a single program, listening to both port and with different parameters, or we can use a single port with multiple parameters.&lt;BR /&gt;&lt;BR /&gt;Is it also possible for your program ?&lt;BR /&gt;May bet there are someadvanced settigns, try asking to the software house.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;   Massimo&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Jul 2003 06:00:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022688#M130855</guid>
      <dc:creator>Massimo Bianchi</dc:creator>
      <dc:date>2003-07-15T06:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: inetd issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022689#M130856</link>
      <description>The programs are Tivoli TMR and Tivoli TEC.&lt;BR /&gt;&lt;BR /&gt;thanx anyway!</description>
      <pubDate>Tue, 15 Jul 2003 09:53:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-issue/m-p/3022689#M130856</guid>
      <dc:creator>Alex Lavrov</dc:creator>
      <dc:date>2003-07-15T09:53:57Z</dc:date>
    </item>
  </channel>
</rss>

