Very Computer

                        echo "Hi there"

and i make it executable with "chmod +x test", if i then type test or ./test
at the command prompt, the script does not execute. it only executes if i type
"source test". why is that? even weirder, if i create another script which
 contains one line,

                        tar cvf - /vmunix | rsh remote_box dd of=/dev/rst0

and make it executable, lo and behold, it works! what's the deal?

:                       echo "Hi there"

: and i make it executable with "chmod +x test", if i then type test or ./test
: at the command prompt, the script does not execute. it only executes if i type
: "source test". why is that? even weirder, if i create another script which
:  contains one line,

:                       tar cvf - /vmunix | rsh remote_box dd of=/dev/rst0

: and make it executable, lo and behold, it works! what's the deal?

Man "test" ... try renaming your script "TEST" and see if if runs
(I'll bet it will!)

Duane
--
     +-------------------------------------------------------------------+

     +-------------------------------------------------------------------+

Call your script something else: "test" is a valid unix command implemented
as a binary executable and often linked to "[" to be used in Bourne/Korn
shell statements like
   if test -f SOMEFILE; then ...; fi           or
   if [ -f SOMEFILE ]; then ....; fi

+---------------------------------------------------------------------+
| Youri N. Podchosov (ynp) * Davidsohn & Son, Inc. NYC * 718-234-4140 |

+---------------------------------------------------------------------+

The problem is the name of the script.

Tnen you run at the command prompt

% test

the '/usr/bin/test' is called because the directory /usr/bin is before the
current directory in the PATH. Your script is not called.

But ./test should work.

So, change the name of the script and it will work.

Igor.

#!/bin/sh

At the head of the script ? If not, then it is not surprising. This line tells
the kernel (AFAIR) to run the rest of the script through the command listed
after the "#!" bit. Naturally, this means that you can also execute other
command interpreter such as perl, awk, sed, etc.

If you didn't have that line, its not surprising that you had to use "source
test" to run the script. Its better to doing things like "sh test" though, as
"source test" just runs the commands as if you've typed the command into the
shell your running in directly... so things can change from shell to shell.
If you use "sh test" then you know what shell is being used.

Quote:>Try altering the name to something else.  Anythign except 'test' as
>'test' is a shell command!

--

Systems Manager and Programmer       |   Total Connectivity Providers Ltd
          I *don't* speak for my company, my boss does that
                      Is there an LD50 for chocolate ?

Just a guess, here, but did you try adding

     #!/bin/sh

to your script?  I'll admit that both scripts work fine on my linux box using
BASH, but it's possible that other shells may treat scripts differently.  I'm
guessing that that may solve your problem as 'echo' is a shell-specific command
while 'tar' is a separate binary.

hth
--
                                   wWw
+-----------------------          (o o)        ------------------------+
|Kurt Granroth          \------ooO-(_)-Ooo-----\                       |
|Computer Science Major  \ Linux: The choice of \ Damn the torpedoes,  |

|Phone: (906) 482-4588     \----------------------\                    |
+---------------------------                       --------------------+
                       http://metro.turnpike.net/G/gran

Quote:>         i'm using SunOS 4.1.3. when i write a shell script called test that
> contains one line:

>                         echo "Hi there"

> and i make it executable with "chmod +x test", if i then type test or ./test
> at the command prompt, the script does not execute. it only executes if i type
> "source test".

--
============================================================================
Sally Woolrich                    |          This mail contains my personal

============================================================================

     Under csh the script works fine using either test or ./test
Under bsh (where test is a command) the script works fine with ./test
but fails with just test.  I believe this is the expected behavior.

     The original poster did not state what shell he was using, but I
can't think of any shell where ./test wouldn't work.  Since he used the
source command, it appears that he is using a csh or one of its
variants.

---

----------

  The Moving FInger write; and, having writ
  Moves on: nor all thy Peity nor Wit
    Shall lure it back to cancel half a Line,
  Nor all thy Tears wash out a Word of it.

: Just a guess, here, but did you try adding

:      #!/bin/sh

: to your script?  I'll admit that both scripts work fine on my linux box using

[rest deleted]

No guys, the reason (I hit the same problem several years ago) is the name
of your script, "test".  There is a Unix utility in /bin/test that is
executed PRIOR to your local "test" program because it is in the PATH first.

Just change the name of your script to ANYTHING not already in the PATH.
When you "source" the program, that looks in the current directory for
"test" not the one in the PATH, /bin/test.
--

URL: http://www.celestial.com         One Mercer Plaza, Suite S100
                                      Mercer Island, WA 98040; (206) 236-1676
Manufacturer of InterRack (Internet-in-a-Rack), a full turn-key
system, including all the hardware, software, installation, setup, training
and support for businesses and Internet Service Providers