topic Re: Executing a Remote Shell Script in Operating System - HP-UX

Executing a Remote Shell Script

Andrew Huizenga — Fri, 12 Jan 2007 11:15:36 GMT

I'm attempting to run a remote shell script from my server on another workstation, but I keep getting the "not found" message anytime I attempt to run the script from my server, but can run it fine on the other server when I'm logged in. I'm using the following line in a local script to try and run the script remotely:

remsh server -l user -n "cd /full/path/of/script/;ls;'callscript $host $dbase $rdg'"

When the "ls" is called I can see the "callscript", but when the script is actually called I get:

sh: callscript host dbase rdg: not found.

Where host, dbase, rdg are values entered by the user. Now, I can take that exact line "callscript host dbase rdg" and it will run succesfully while I'm logged into the remote workstation. The workstations .rhosts file is updated with:

myserver myusername
+ myusername

Any advice on what I need to add to my local script to run the remote script successfully?

Thanks.

Re: Executing a Remote Shell Script

Geoff Wild — Fri, 12 Jan 2007 11:21:10 GMT

Instead of callscript use full path:

/full/path/of/script/callscript

. and /full/path/of/script/ are in in the default PATH - and . should NEVER be.

Rdgs...Geoff

Re: Executing a Remote Shell Script

Peter Nikitka — Fri, 12 Jan 2007 11:28:41 GMT

Hi,

change your command line to use the pathname and drop the wrong usage of the single quotes:

remsh server -l user -n "cd /full/path/of/script/;ls;./callscript $host $dbase $rdg"

Your attempt tries to locate a program
'callscript host dbase rdg' (spaces are part of the program name!) via the PATH variable.

mfG Peter

Re: Executing a Remote Shell Script

Andrew Huizenga — Fri, 12 Jan 2007 11:29:09 GMT

This time I get:

sh: /home/gp7200/550-PROD/scripts/callPRODscripts 10.31.152.94 3424 7374: not found.

Modified the script to have:

remsh server -l user -n "'/full/name/of/path/callscript $host $dbase $rdg'"

Re: Executing a Remote Shell Script

Andrew Huizenga — Fri, 12 Jan 2007 11:34:23 GMT

Peter-

I modified the line to:

remsh server -l user -n "/full/name/of/path/callscript $host $dbase $rdg"

And now receive:

/full/name/of/path/callscript: expect: not found.

In the remote script "callscript", I'm using the "expect" function- is there something in my local script I need to add to specify a location of "expect"?

Re: Executing a Remote Shell Script

Peter Nikitka — Fri, 12 Jan 2007 12:01:51 GMT

Hi Andrew,

it is good practise to check for the existence of non-standard tools, which you are using in scripts.
If its a ksh script, you can do it like this:
#
if ! whence expect >/dev/null
then PATH=$PATH:/path/where/tools_are_found
fi

If you have a setup of an environment commonly used after a normal login (e.g. /usr/local/env/common.env), you could source it explicitly in your remsh-command:

remsh server -l user -n ". /usr/local/env/common.env; cd /full/path/of/script/;ls;./callscript $host $dbase $rdg"

mfG Peter

Re: Executing a Remote Shell Script

Andrew Huizenga — Fri, 12 Jan 2007 12:13:20 GMT

I guess I'm a bit confused- when I'm using remsh, I thought it was just the same as being logged into the remote server and running the script. Is it assuming the the "expect" function on the remote server is in the same location as my local server?

Re: Executing a Remote Shell Script

Peter Nikitka — Fri, 12 Jan 2007 12:25:11 GMT

Hi,

you can check:

echo $PATH
remsh -l user -n 'echo $PATH'

Reasons:
- it's another user, you are connected to
- it's a remote server and your toolpath may vary
- it's not an interactive session you are using, so some setting may not be done

mfG Peter

Re: Executing a Remote Shell Script

Andrew Huizenga — Fri, 12 Jan 2007 14:19:54 GMT

Okay. When I run the echo $PATH on the local server, and then the remote server using remsh, I get the same result. However, when I log into the other server (as a different user not the same as my local server), I get a different result.

I did a "which expect" on both servers, and the expect function appears to be located in the same directory on both (/apps/bin/expect).

I guess I'm still confused as to why I'm getting that "not found" message if "expect" is located in the same place on both servers.

Re: Executing a Remote Shell Script

OldSchool — Fri, 12 Jan 2007 14:39:41 GMT

the question is really "what is $PATH for the user id, on the remote server, that is attempting to run the command"

usually, I just set the path to what I need it to be in the script and be done with it.............

Re: Executing a Remote Shell Script

Geoff Wild — Fri, 12 Jan 2007 15:04:39 GMT

In your script - hard code the calls to other apps:

/usr/local/bin/expect

not

expect

Rgds...Geoff

Re: Executing a Remote Shell Script

Andrew Huizenga — Fri, 12 Jan 2007 15:18:02 GMT

Thanks, hardcoding worked!

Re: Executing a Remote Shell Script

Geoff Wild — Fri, 12 Jan 2007 16:40:55 GMT

No worries Andrew.

PS - welcome to the forums!

Please have a read through:

http://forums1.itrc.hp.com/service/forums/helptips.do?#28

Basically, points help people determine the relevance of the answer when they search the ITRC for similar questions.

Also, it is a good idea to close a thread when you are satisfied with the answers.

Thanks...Geoff

Re: Executing a Remote Shell Script

Bill Hassell — Fri, 12 Jan 2007 17:35:15 GMT

Good script writing dictates that NO assumptions are made about the environment. The remsh environment is not set as if you logged in because remsh does not login -- instead, it validates that your request has been validated and then sets a minimal environment. The same is true for cron and other batch operations. So there are three mandatory statements at the beginning of every script you write:

#!/usr/bin/sh
set -u
export PATH=/usr/bin:/usr/contrib/bin....

The first defines the correct shell to use for interpreting the script. The second line prevents spelling errors for variables by stopping the script. The third defines the PATH required for this script. You add only the paths needed for your script. This PATH only exists inside your script. You can hardcode full pathnames in your scripts but it is a lot of extra work -- that's why defining PATH locally makes more sense. Additionally, PATH is a potential security risk so your scripts should never use the currently defined PATH value.

You also look at your required environment variables. To see what is currently defined, use the env command, then pick the ones needed by your script.

Re: Executing a Remote Shell Script

Andrew Huizenga — Tue, 16 Jan 2007 13:57:11 GMT

Thanks!