02-20-2007
Quote:
Originally Posted by Lika
Hello,
I would like to do a rexec to execute a C exe (prog.e) :
rexec -l user -p password host prog.e
When I execute this command, I have this error :
prog.e : can not find lib.o
But, When I execute prog.e directly in the remote machine : well done ! No error output.
Thks for your help !
There are two ways of dealing with this. One way is to compile prog.e
statically. You must refer to your compiler documentation to learn how to do this, but you can always just try compiling with "-static" and see what happens.
Unfortunately, some compilers still output an executable which depends on a small shared library, provided with the compiler. So you can always use method two, which is this: Invoke the program as an argument to the
env command. The
env command allows you to specify environment variables and their values for the program you want to run. You might be familiar with this syntax (from sh, bash, ksh):
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/lib:/usr/local/lib $PWD/myprogram arg1 arg2
This problem is that this will not work for remote execution -- the rexec command uses these values, but the remote side reinitializes the values. The solution is env:
env LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/lib $PWD/myprogram arg1 arg2
Works the same way, but
now you can prefix your
rexec command to the whole thing like this:
rexec -l user -p password host env LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/lib $PWD/myprogram arg1 arg2
By the way, the "$HOME/lib" is for "demo" purposes only. So here's what you should do in "the general case":
rexec -l user -p password host env LD_LIBRARY_PATH="$LD_LIBRARY_PATH" PATH="$PATH" myprogram arg1 arg2
Since that might be a bit lengthy, you can create a shell function (or script) to do the ugly work for you:
HTML Code:
myrexec() {
user="$1"
pass="$2"
host="$3"
shift 3
rexec -l $user -p $pass $host \
env LD_LIBRARY_PATH="$LD_LIBRARY_PATH" PATH="$PATH" \
"$@" ;
}
Throw this into your .bashrc file, then you can do:
myrexec username password hostname command arg1 arg2
Good luck
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
In http://forums.unix.com/showthread.php?threadid=391
there is one statement called expect.
but when I issue command whereis expect, respond from o/s only EXPECT: (only one world).
I try to find it at /usr/bin, no expect statement there ?
is it default unix o/s command ?
I am using AIX on... (1 Reply)
Discussion started by: yatno
1 Replies
2. UNIX for Dummies Questions & Answers
Can someone tell me how I would enable Rexec on a UNIX machine? And is the procedure different on the different systems - Solaris, HP-UX -etc.
Thanks~!!
mike (1 Reply)
Discussion started by: raichuu
1 Replies
3. Programming
At time of installation I have to open the resource. and i have to insert a string serial number in the exe.
please provide me code to edit the exe (in solaris) to insert a serial number which can be used by exe at run time. (6 Replies)
Discussion started by: ssahu
6 Replies
4. Solaris
How is rexec enabled on a Solaris 8?
How can I check if rexec is installed? (1 Reply)
Discussion started by: pmj1970
1 Replies
5. UNIX for Dummies Questions & Answers
Hi folks!
my client uses an winapplication which is launching shell-scripts remotely on a HP-Unix Machine via Rexec.
The application-configuration is launching the script (which is in the home directory of connecting user) like:
rexec host user pass shell.sh
So far so good, everything... (3 Replies)
Discussion started by: JohnMurdoch
3 Replies
6. Programming
Hello,
I 've trie to execute a a program with parameters unsuccessfully and i take the above message :
"The system cannot find the path specified."
I used a variaton of the above command :
system("\"C:\\xxx\\xxx\\xxx.exe -xxx -xxx xxx.xxx xxx.xxx xxx.xxx\"");
Thanks in advance (4 Replies)
Discussion started by: eusta
4 Replies
7. AIX
Rexec executes commands one at a time on a remote host. The rexec command provides an automatic login feature by checking for a $HOME/.netrc file. User and password are stored
in $HOME/.netrc.
I would like to log on to another host and execute a script/command but not using $HOME/.netrc file,... (4 Replies)
Discussion started by: ioniCoder
4 Replies
8. UNIX for Advanced & Expert Users
Hi Team,
I am executing some ksh scripts which inturn calls java files in AIX Environment. We have installed java6_64 which is in .profile. But when we execute from rexec its taking path from some different place that does not have java in $PATH variable. Can you please help me find out which... (2 Replies)
Discussion started by: balasubramani04
2 Replies
9. Shell Programming and Scripting
I want to execute a qt exe program at startup. That is after automatic login instead of loading Desktop and seeing it, the program quickly pop up to the screen. For this, I think we should add the script to rcx.local rather than rc.local I guess though.. I tried adding a script to /etc/rc.local... (0 Replies)
Discussion started by: dr_mabuse
0 Replies
10. UNIX for Dummies Questions & Answers
Hello all,
Am facing a peculiar problem, I have copied a utility exe from a bin folder into my local temp folder. I am trying to execute that exe, but it throws out an error saying "No such file or directory".
I have given 755 & 777 permissions to it and I tried, but it still throws out that... (6 Replies)
Discussion started by: abhisheksunkari
6 Replies
REXEC(1) General Commands Manual REXEC(1)
NAME
rexec -- remote execution client for an exec server
SYNOPSIS
rexec [ -abcdhns -l username -p password ] host command
DESCRIPTION
Rexec calls the rexec(3) routine to act as a client for the remote host's rexecd(8) server.
It asks that ``command'' be run on the host computer, using username/password authentication. See rexec(3) and rexecd(8) for details of the
protocol.
OPTIONS
Rexec accepts several options, but only three are likely to be very useful:
-l username
Set the log-in name on the remote host to username.
-p password
Provide the password for the remote account. The command line argument will be blanked after being parsed, to prevent it from being
seen with ps(1). However, it is still not very secure to type the password on the command line. In particular, be sure that the
shell's history file is protected.
-n Explicitly prompt for name and password, even if provided in the environment, in the $HOME/.netrc file, or in the environmental
variables REXEC_USER and REXEC_PASS.
Other options that might be useful with non-standard remote exec daemons, or to debug connections:
-a Do not set up an auxiliary channel for standard error from command; the remote standard error and output are then both returned on
the local standard output. By default, rexec asks that a separate channel be set up for diagnostic output from the remote command.
-b Use signal handling as in BSD rsh(1). Only the signals SIGINT, SIGQUIT, and SIGTERM are echoed to the remote process. They do not
remain raised locally, so rexec waits for the remote command to shutdown its side of the socket. Also, CNTRL-Z will only suspend
execution locally--the remote command may continue to run.
-c Do not close remote standard input when local standard input closes. Normally the standard input to the remote command is closed
when the local standard input is closed.
-d Turn on debugging information. In particular the command sent to the remote host will be echoed.
-h Print a usage message.
-s Do not echo signals received by the rexec onto the remote process. Normally, signals which can be trapped are passed on to the
remote process; then, when you type CNTRL-C, the remote process terminates as well.
USERNAME AND PASSWORD
Rexec(1) searches for the username and password in the following order:
1. If -n is given on the command line, the user will always be prompted for both, even if they are also given on the command line.
2. The command line will be parsed
3. If the environmental variables REXEC_USER or REXEC_PASS are defined, they will define the username or password.
4. The $HOME/.netrc file will be searched. See ftp(1) for a description of this file's format.
5. Finally, the user will be prompted if either the username or password remains undefined.
SECURITY
Users of this command should be aware that rexec(3) transmits their password to the remote host clear text, not encrypted. If the network
is not secure to the remote host, the password can be comprimised.
SIGNALS
Without the -b option, all signals which can be handled are echoed to the remote process. Afterwards, however, they remain raised in the
local process. Typically, this means that rexec(1) will exit after receiving a fatal signal, even if the remote process has arranged to
handle or ignore it.
Differing operating systems use differing signal numbers; for example AIX and SunOS use 18 for SIGTSTP (^Z), while Linux uses 20. There-
fore, it may have a different effect remotely than locally. In particular, typing CNTL-Z may not suspend the execution of the remote
process.
EXAMPLE
rexec othermachine cat ">remote_file; date" <local_file
will send local_file to the othermachine as remote_file.
BUGS
Please send bug reports, system incompatibilities, and job offers to the author.
SEE ALSO
rexec(3), rexecd(8), rsh(1)
AUTHOR
Michael Sadd
mas22@cornell.edu
http://www.tc.cornell.edu/~sadd/
Thanks to Orange Gopher (2/10/97) and Johannes Plass (plass@dipmza.physik.uni-mainz.de, Oct. 17 1996) for useful suggestions.
February 14, 1997 REXEC(1)