<?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: call shell script with . ./myscript.sh in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085280#M441389</link>
    <description>And without the extra ., it simply means to look in the current directory ($PWD) to find "myscript.sh.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
    <pubDate>Thu, 20 Dec 2007 15:25:38 GMT</pubDate>
    <dc:creator>Pete Randall</dc:creator>
    <dc:date>2007-12-20T15:25:38Z</dc:date>
    <item>
      <title>call shell script with . ./myscript.sh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085278#M441387</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Why sometimes some scripts needs to be call with the . ./myscript.sh syntax and sometimes with the ./myscript.sh ?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;Regards&lt;BR /&gt;Den</description>
      <pubDate>Thu, 20 Dec 2007 15:21:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085278#M441387</guid>
      <dc:creator>Leo The Cat</dc:creator>
      <dc:date>2007-12-20T15:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: call shell script with . ./myscript.sh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085279#M441388</link>
      <description>The extra . causes the script to run without invoking a new shell.&lt;BR /&gt;&lt;BR /&gt;Mark Syder (like the drink but spelt different)</description>
      <pubDate>Thu, 20 Dec 2007 15:23:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085279#M441388</guid>
      <dc:creator>MarkSyder</dc:creator>
      <dc:date>2007-12-20T15:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: call shell script with . ./myscript.sh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085280#M441389</link>
      <description>And without the extra ., it simply means to look in the current directory ($PWD) to find "myscript.sh.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Thu, 20 Dec 2007 15:25:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085280#M441389</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2007-12-20T15:25:38Z</dc:date>
    </item>
    <item>
      <title>Re: call shell script with . ./myscript.sh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085281#M441390</link>
      <description>That was poorly worded.  &lt;BR /&gt;&lt;BR /&gt;In either case, the single period immediately preceding /myscript.sh means to look in the current directory.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Thu, 20 Dec 2007 15:26:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085281#M441390</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2007-12-20T15:26:58Z</dc:date>
    </item>
    <item>
      <title>Re: call shell script with . ./myscript.sh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085282#M441391</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;What could be the consequences to launch another shell ?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Den</description>
      <pubDate>Thu, 20 Dec 2007 15:36:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085282#M441391</guid>
      <dc:creator>Leo The Cat</dc:creator>
      <dc:date>2007-12-20T15:36:57Z</dc:date>
    </item>
    <item>
      <title>Re: call shell script with . ./myscript.sh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085283#M441392</link>
      <description>&lt;!--!*#--&gt;Read the manpage of sh-posix(1) for details. Relevant portion posted below:&lt;BR /&gt;&lt;BR /&gt;sh-posix(1)&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;% . file [arg]...&lt;BR /&gt;&lt;BR /&gt;           (period)  Read and execute commands from file and return.  The&lt;BR /&gt;           commands are executed in the current shell environment.  The&lt;BR /&gt;           search path specified by PATH is used to find the directory&lt;BR /&gt;           containing file.  If any arguments arg are given, they become the&lt;BR /&gt;           positional parameters.  Otherwise, the positional parameters are&lt;BR /&gt;           unchanged.  The exit status is the exit status of the last&lt;BR /&gt;           command executed.</description>
      <pubDate>Thu, 20 Dec 2007 15:41:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085283#M441392</guid>
      <dc:creator>Sandman!</dc:creator>
      <dc:date>2007-12-20T15:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: call shell script with . ./myscript.sh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085284#M441393</link>
      <description>Hi Den:&lt;BR /&gt;&lt;BR /&gt;The dot-space-filename (whether or not the filename contains a relative path of "./" means that you want to *source* or read the contents of the file into your *current* environment without starting a new shell (and thus losing the variable values).&lt;BR /&gt;&lt;BR /&gt;Sourcing is done to pass environmental variables defined in a file into the environment of another:&lt;BR /&gt;&lt;BR /&gt;# cat mythings&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;export NAME=Den&lt;BR /&gt;&lt;BR /&gt;# cat someshell&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;. ./mythings&lt;BR /&gt;echo "I am ${NAME}"&lt;BR /&gt;exit 0&lt;BR /&gt;&lt;BR /&gt;To see the difference, run 'someshell'; then change the line that reads:&lt;BR /&gt;&lt;BR /&gt;. ./mythings&lt;BR /&gt;&lt;BR /&gt;TO:&lt;BR /&gt;&lt;BR /&gt;./mythings&lt;BR /&gt;&lt;BR /&gt;...and run 'someshell' again.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Thu, 20 Dec 2007 15:46:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085284#M441393</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2007-12-20T15:46:35Z</dc:date>
    </item>
    <item>
      <title>Re: call shell script with . ./myscript.sh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085285#M441394</link>
      <description>Typically scripts are not sourced and need to be executable.  Files that are sourced are typically the shell env files (for aliases and functions) and just need to be readable.</description>
      <pubDate>Fri, 21 Dec 2007 08:29:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085285#M441394</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-12-21T08:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: call shell script with . ./myscript.sh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085286#M441395</link>
      <description>Answer was various and good.</description>
      <pubDate>Tue, 06 May 2008 00:20:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/call-shell-script-with-myscript-sh/m-p/5085286#M441395</guid>
      <dc:creator>Leo The Cat</dc:creator>
      <dc:date>2008-05-06T00:20:05Z</dc:date>
    </item>
  </channel>
</rss>

