11-05-2008
I don't know how to make ksh behave the way you want. The best I can come up with is to send a command to the remote system to run a command and put the output in a remote file. Then use ftp to retrieve the file and examine the contents. It's not pretty but it works in environments where freeware is not available.
This stuff is much easier with openssh and that is what I do these days. No complex co-process or exec statements are needed. And it's much more secure.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello everybody,
I have a question about I/O redirection within a coprocess.
I want to setup a coprocess and then redirect output to a file on a remote machine.
Here's some Perderabo code modified
exec 4>&1
#
# Section 1 --- Prove that we can talk with the hosts in HOSTLIST
# ... (4 Replies)
Discussion started by: Mugin
4 Replies
2. Shell Programming and Scripting
I am wracking my brains over this. I am trying to use a Korn Shell script to execute an Oracle PL/SQL procedure, using the Oracle command line interface (sqlplus). The script starts sqlplus in a coprocess, and the two processes communicate using a two-way pipe. The bgnice option is off, so both... (8 Replies)
Discussion started by: Mark Puddephat
8 Replies
3. Shell Programming and Scripting
Hi can any one let me know if awk doesnt work with the coprocess??? I have tried a simple example mentioned below but couldnt get it working seems like awk doesnt work with the coprocess concept. I would appreciate very much for any inputs on this.
exec 4>&1
awk -v count=$COUNT >&4 2>&4 |&... (6 Replies)
Discussion started by: ahmedwaseem2000
6 Replies
4. UNIX for Dummies Questions & Answers
Hello,
I'm trying to assign a numeric value that is returned from one of my programs to a variable in tcsh. I want to do:
@ r10 = './my_prog file 35'
where ./my_prog file 35 returns a decimal value, but this doesn't work. How do I achieve the desired result?
Janet (4 Replies)
Discussion started by: psran
4 Replies
5. Shell Programming and Scripting
Hi there,
I want to connect to a Cisco router with a KSH script via coprocess:
telnet 192.168.2.82|&
print -p “login”
print -p "password"
With telnet it works. Now I want to use SSH:
ssh -T -l login 192.168.2.82|&
print -p "password"
The router answer me I enter a bad... (7 Replies)
Discussion started by: sylvainkalache
7 Replies
6. Shell Programming and Scripting
Hello,
There is pipe chain and I want concacenate piped data with some variable:
balh blah| ... $var1
What command I should use instead ... to concatenate piped output with $var1. I think I coud solve this using temp var - but could it be done in one line like sample above ?
thanks... (4 Replies)
Discussion started by: vilius
4 Replies
7. Shell Programming and Scripting
While assisting a forum member, I recommended running SQL/Plus in a coprocess (to make database connections and run a test script) for the duration of his script rather than starting/stopping it once for every row in a file he was processing.
I recalled I made a coprocess example for folks at... (2 Replies)
Discussion started by: gary_w
2 Replies
8. Shell Programming and Scripting
Hi,
Please help to seprate my /var/adm/messages output. Than i want to take this
output in the excel.
e,g
cat /var/adm/messages
Sep 4 10:16:52 ibsadm1 inetd: vnetd from 172.17.5.20 38353
Sep 4 10:16:52 ibsadm1 inetd: bpcd from 172.17.5.20 915
Sep 4 10:16:55 ibsadm1 inetd: ... (5 Replies)
Discussion started by: nirjhar17
5 Replies
9. UNIX for Advanced & Expert Users
Hi all,
I have F5 load balancer on my system and checking service status by opening an ftp session in every 30 seconds. These ftp sessions are being logged in /var/adm/wtmpx and filling up the file. when i run the last command most of the output is this ftp session. I was wondering if there is a... (1 Reply)
Discussion started by: cepxat
1 Replies
10. Shell Programming and Scripting
Hi
I have this command, which counts number of lines in a specific file and then prints it on screen.nawk 'NF{c++}END{print "Number of GPS coordinates in file: "c}' $filename
I would like to have the output put into a variable, but can't seem to find the correct argument for it.
How do I... (3 Replies)
Discussion started by: bulleteyedk
3 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)