<?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: Setting environment variables in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517760#M871233</link>
    <description>Above statements are good, but one more thing to remember consider.&lt;BR /&gt;&lt;BR /&gt;If you modify the .profile and are using CDE, you need to make sure the DTSOURCEPROFILE=TRUE in the .dtprofile.  This cause the .profile to be read when you open a terminal.&lt;BR /&gt;&lt;BR /&gt;...jcd...</description>
    <pubDate>Tue, 17 Apr 2001 14:47:47 GMT</pubDate>
    <dc:creator>Joseph C. Denman</dc:creator>
    <dc:date>2001-04-17T14:47:47Z</dc:date>
    <item>
      <title>Setting environment variables</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517755#M871228</link>
      <description>I would like to set environment variables that don't disappear just because I have closed and reopened a terminal window, but how? The book's instructions don't help. Also, is it possible to set an environment variable on one terminal window and see the changes on another one?&lt;BR /&gt;&lt;BR /&gt;As an example, I have perl in /opt/perl5 and would like to make this available from everywhere...&lt;BR /&gt;&lt;BR /&gt;Thank you,&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Tue, 17 Apr 2001 13:17:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517755#M871228</guid>
      <dc:creator>Pete Mattison</dc:creator>
      <dc:date>2001-04-17T13:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: Setting environment variables</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517756#M871229</link>
      <description>set them up in your .profile via the &lt;BR /&gt;export VALUE=whatever&lt;BR /&gt;&lt;BR /&gt;#echo $VALUE&lt;BR /&gt;whatever&lt;BR /&gt;&lt;BR /&gt;(setenv in csh)&lt;BR /&gt;&lt;BR /&gt;this will ensure that your shell will set them up even if you fork other shells.&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Tue, 17 Apr 2001 13:23:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517756#M871229</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-04-17T13:23:25Z</dc:date>
    </item>
    <item>
      <title>Re: Setting environment variables</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517757#M871230</link>
      <description>Hi, make sure you export all the variables you want your child shells to inherit.  Example - Set Up Shell Variables:&lt;BR /&gt;        EDITOR=vi&lt;BR /&gt;        LANG=c&lt;BR /&gt;        HISTSIZE=201&lt;BR /&gt;        HISTFILE=$HOME/.sh_history&lt;BR /&gt;        ORGANIZATION="Genzyme Biosurgery" &lt;BR /&gt;        LPDEST=RRA106&lt;BR /&gt;export EDITOR LANG HISTSIZE HISTFILE ORGANIZATION LPDEST&lt;BR /&gt;&lt;BR /&gt;Now any window you open will have these variables set.  Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Rob &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Apr 2001 13:33:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517757#M871230</guid>
      <dc:creator>Rob Smith</dc:creator>
      <dc:date>2001-04-17T13:33:50Z</dc:date>
    </item>
    <item>
      <title>Re: Setting environment variables</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517758#M871231</link>
      <description>First you have to realize a few things about environment variables. The export goes only one way from parent to child. If you set a var e.g. MYVAR=xxx in a process and export MYVAR&lt;BR /&gt;you will see the value xxx in the parent and all child shells or processes. However, if you&lt;BR /&gt;set MYVAR=yyy in a child process and export it, the parent will still see the value 'xxx'.&lt;BR /&gt;If you really need bidirectional setting of&lt;BR /&gt;values you will need to use files or pipes.&lt;BR /&gt;For simple things like PATH, you can use the .profile's for each user or if it truly global set a value in /etc/profile. /etc/profile can be used to set a variable and export it to everyone. You can also define global PATH's and MANPATH's by setting them in /etc/PATH and /etc/MANPATH.</description>
      <pubDate>Tue, 17 Apr 2001 13:36:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517758#M871231</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-04-17T13:36:48Z</dc:date>
    </item>
    <item>
      <title>Re: Setting environment variables</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517759#M871232</link>
      <description>Good morning, Pete.&lt;BR /&gt;&lt;BR /&gt;There's a few global environment files that are available in /etc which you can use to set an environment globally for all users (at least, from what I can see in HP/UX 11.00...):&lt;BR /&gt;&lt;BR /&gt;/etc/PATH : Set global PATH parameter&lt;BR /&gt;/etc/MANPATH : Set global MANPATH parameter&lt;BR /&gt;/etc/SHLIB_PATH : Set global shared library PATH&lt;BR /&gt;/etc/profile : Generic system-wide profile. Normally kept to the bare minimum of what every user needs. /etc/profile normally sources /etc/PATH and /etc/MANPATH. &lt;BR /&gt;&lt;BR /&gt;Follow the same steps (for exporting the variable) that Bill shows above. In /etc/profile, this is for /usr/bin/sh initialization, so no C shell here! &lt;GRIN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/GRIN&gt;</description>
      <pubDate>Tue, 17 Apr 2001 13:40:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517759#M871232</guid>
      <dc:creator>James Martens</dc:creator>
      <dc:date>2001-04-17T13:40:06Z</dc:date>
    </item>
    <item>
      <title>Re: Setting environment variables</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517760#M871233</link>
      <description>Above statements are good, but one more thing to remember consider.&lt;BR /&gt;&lt;BR /&gt;If you modify the .profile and are using CDE, you need to make sure the DTSOURCEPROFILE=TRUE in the .dtprofile.  This cause the .profile to be read when you open a terminal.&lt;BR /&gt;&lt;BR /&gt;...jcd...</description>
      <pubDate>Tue, 17 Apr 2001 14:47:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/setting-environment-variables/m-p/2517760#M871233</guid>
      <dc:creator>Joseph C. Denman</dc:creator>
      <dc:date>2001-04-17T14:47:47Z</dc:date>
    </item>
  </channel>
</rss>

