<?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: echodo not working. in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571076#M873170</link>
    <description>Ramesh:&lt;BR /&gt;I did all 3 of your commands and they returned the same thing. /p/util/oracle/8.0.6/bin/echodo&lt;BR /&gt;Here are the only 2 working lines in the echodo script.&lt;BR /&gt;&lt;BR /&gt;echo $*&lt;BR /&gt;$*&lt;BR /&gt;This should be echoing the command and then execute it.&lt;BR /&gt;Thanx.</description>
    <pubDate>Tue, 28 Aug 2001 13:10:19 GMT</pubDate>
    <dc:creator>Colin Summers</dc:creator>
    <dc:date>2001-08-28T13:10:19Z</dc:date>
    <item>
      <title>echodo not working.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571074#M873168</link>
      <description>I have several scripts that use echodo. 4 some reason they have stopped working and it's the echodo that is failing. I have tested this on the command line and found that all of the commands, ie cat ls -al, mkdir, rmdir, work EXCEPT export. &lt;BR /&gt;example:&lt;BR /&gt;1.echodo ls -l /tmp  - this works&lt;BR /&gt;2. echodo mkdir /tmp/colin - this works&lt;BR /&gt;3. echodo export COLIN="TEST77" then I echo   $COLIN and it's empty.&lt;BR /&gt;I can't figure out why. No changes to the O/S. Any ideas would be of great help.&lt;BR /&gt;Thank you all in advance.</description>
      <pubDate>Mon, 27 Aug 2001 22:00:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571074#M873168</guid>
      <dc:creator>Colin Summers</dc:creator>
      <dc:date>2001-08-27T22:00:46Z</dc:date>
    </item>
    <item>
      <title>Re: echodo not working.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571075#M873169</link>
      <description>Hi Colin,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;AFAIK, there is no such command called echodo&lt;BR /&gt;you might be using an alias or a wrapper script.&lt;BR /&gt; Can you do "type echodo" or "whence echodo" or "which echodo" and see what is echodo&lt;BR /&gt;&lt;BR /&gt;If it is an alias "type echodo" will return&lt;BR /&gt;echodo is an alias for .......&lt;BR /&gt;&lt;BR /&gt;-Ramesh</description>
      <pubDate>Mon, 27 Aug 2001 22:15:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571075#M873169</guid>
      <dc:creator>linuxfan</dc:creator>
      <dc:date>2001-08-27T22:15:19Z</dc:date>
    </item>
    <item>
      <title>Re: echodo not working.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571076#M873170</link>
      <description>Ramesh:&lt;BR /&gt;I did all 3 of your commands and they returned the same thing. /p/util/oracle/8.0.6/bin/echodo&lt;BR /&gt;Here are the only 2 working lines in the echodo script.&lt;BR /&gt;&lt;BR /&gt;echo $*&lt;BR /&gt;$*&lt;BR /&gt;This should be echoing the command and then execute it.&lt;BR /&gt;Thanx.</description>
      <pubDate>Tue, 28 Aug 2001 13:10:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571076#M873170</guid>
      <dc:creator>Colin Summers</dc:creator>
      <dc:date>2001-08-28T13:10:19Z</dc:date>
    </item>
    <item>
      <title>Re: echodo not working.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571077#M873171</link>
      <description>echodo is a script supplied as part of the&lt;BR /&gt;oracle distribution, so is not standard hp-ux.&lt;BR /&gt;All it does is to echo a command and then&lt;BR /&gt;execute it, using:&lt;BR /&gt;  echo $*&lt;BR /&gt;  $*&lt;BR /&gt;&lt;BR /&gt;Since it is a script, each time it is invoked &lt;BR /&gt;it runs in its own subshell, so your &lt;BR /&gt;"export COLIN=TEST77" command *does* get &lt;BR /&gt;executed, but within its own subshell which then immediately exits.&lt;BR /&gt;&lt;BR /&gt;When you do "echo $COLIN" from the calling&lt;BR /&gt;shell, COLIN is therefore undefined.&lt;BR /&gt;&lt;BR /&gt;Therefore echodo is of no use if you are issuing commands which affect the shell environment.&lt;BR /&gt;&lt;BR /&gt;echodo always works this way, nothing has changed on your system. The only way round it is to take out the echodo before the export.&lt;BR /&gt;How about &lt;BR /&gt;  export COLIN="TEST77" &lt;BR /&gt;  echo $COLIN&lt;BR /&gt;in your script.&lt;BR /&gt;Hope this helps.&lt;BR /&gt;Graham</description>
      <pubDate>Tue, 28 Aug 2001 13:32:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571077#M873171</guid>
      <dc:creator>Graham Cameron_1</dc:creator>
      <dc:date>2001-08-28T13:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: echodo not working.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571078#M873172</link>
      <description>Hi Colin,&lt;BR /&gt;&lt;BR /&gt;Graham has already explained to you as to why your variable is not getting set in your shell, I just wanted to add that if you are trying to set a variable just add it to user's .profile in $HOME/.profile&lt;BR /&gt;&lt;BR /&gt;-HTH&lt;BR /&gt;Ramesh</description>
      <pubDate>Tue, 28 Aug 2001 13:56:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/echodo-not-working/m-p/2571078#M873172</guid>
      <dc:creator>linuxfan</dc:creator>
      <dc:date>2001-08-28T13:56:50Z</dc:date>
    </item>
  </channel>
</rss>

