<?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 inetd environment in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-environment/m-p/3494430#M215599</link>
    <description>I'd like to pass a few of specific environment variables to servers started by inetd.&lt;BR /&gt;What is the best way to do it?</description>
    <pubDate>Mon, 28 Feb 2005 12:35:29 GMT</pubDate>
    <dc:creator>Domenico Viggiani</dc:creator>
    <dc:date>2005-02-28T12:35:29Z</dc:date>
    <item>
      <title>inetd environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-environment/m-p/3494430#M215599</link>
      <description>I'd like to pass a few of specific environment variables to servers started by inetd.&lt;BR /&gt;What is the best way to do it?</description>
      <pubDate>Mon, 28 Feb 2005 12:35:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-environment/m-p/3494430#M215599</guid>
      <dc:creator>Domenico Viggiani</dc:creator>
      <dc:date>2005-02-28T12:35:29Z</dc:date>
    </item>
    <item>
      <title>Re: inetd environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-environment/m-p/3494431#M215600</link>
      <description>You can try modifying the /sbin/init.d/inetd script and put your export statements before then inetd invocation in the start) section. I'm don't know if inetd does a subsequent putenv() that would wipe out any unexpected env variables.</description>
      <pubDate>Mon, 28 Feb 2005 12:46:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-environment/m-p/3494431#M215600</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-02-28T12:46:43Z</dc:date>
    </item>
    <item>
      <title>Re: inetd environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-environment/m-p/3494432#M215601</link>
      <description>Hey Domenico,&lt;BR /&gt;You should edit /etc/inetd.conf and add the env variables you want the services to run with ... this will allow the daemon to run with the specific parameter from within inetd.</description>
      <pubDate>Mon, 28 Feb 2005 13:07:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-environment/m-p/3494432#M215601</guid>
      <dc:creator>Dani Seely</dc:creator>
      <dc:date>2005-02-28T13:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: inetd environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-environment/m-p/3494433#M215602</link>
      <description>You could edit the inetd file in /sbin/init.d but this file may be replaced at any time in the future by a patch. Configurations for startup scripts (like inetd) are handled in the /etc/rc.config.d directory. There is no specific inetd file in that directory so you can add the new env values in /etc/rc.config to a new file called /etc/rc.config.d/inetd. whatever is in that script will be added to the startup environment.</description>
      <pubDate>Mon, 28 Feb 2005 23:18:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-environment/m-p/3494433#M215602</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-02-28T23:18:22Z</dc:date>
    </item>
  </channel>
</rss>

