The diff command is not equipped to handle files residing on remote hosts. There are a few ways that you could go about this. All involve getting the remote file to the local host, or sending the local file to the remote host.
This is how you can do it using rsh:
This is how you can do it using ssh:
Note that the '>' will create a file named /tmp/remote_file on the local system. To create remote files using either rsh or ssh, you have to escape the '>' as '\>'
Hi all,
i am copying .gz files from production server to development server using
"scp" command.my requirement is after copying .gz files i want to delete old
.gz files(two days back) in development server from production server.
like this way i need to delelte .log ,.z and .dmp files... (3 Replies)
Hi
I have a different architecture for my perl application.
I have apache one server and data on another(not database).
i need to read the data from other machine and that too securely.
Also opening ports on apache machine is also restricted.
Can anyone help me on this (2 Replies)
i want a script with expect or perl or shell which will do ssh to remote host...it will take commandline argument and run the script in remote host.......
i.e that will be like ./ssh.exp remoteip username passwd /tmp.kk.sh
can someone help me on this? (1 Reply)
I want to write a script which would run from one host say A and connect to other remote host B and then run rest of commands in that host. I tried connecting from A host to B with SSH but after connecting to host B it just getting me inside Host B command prompt. Rest of the script is not running... (6 Replies)
Gurus/Experts
We have a centralized UNIX/Solaris server from where we can actually ssh to all other UNIX/Solaris servers...I need to write a script that reside on this centerlized server and do FileSystem monitoring (basically run df -h or -k) of other remote servers and then send an email to me... (6 Replies)
I do a ssh to remote host(A1) from local host(L1). I then ssh to another remote(A2) from A1.
When I do a who -m from A2, I see the "connected from" as "A1".
=> who -m
userid pts/2 2010-03-27 08:47 (A1)
I want to identify who is the local host who initiated the connection to... (3 Replies)
Hi,
I wish to run a script located on a remote host machineB from machineA.
I am using ssh and running the below on machineA.
However, the ssh does not seem to work and freezes at
ssh -l wlsadmin machineB -v
Sun_SSH_1.1.2, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
debug1: Reading... (9 Replies)
Checking crontab job entry in 3 different hosts Hi Gurus,
I am trying to connect to remote host from current host to check crontab entries. I have started like this
ssh -n -l db2psp 205.191.156.17 ". ~/.profile >/dev/null 2>/dev/null; cd log ;ls | wc -l"
I got this error ?
ssh:... (1 Reply)
Hi,
Given addresses of 2 remote machines, using a shell script is it possible to
get the state of running processes in "src"
stop all the processes in "src"
exit out of "src"
ssh into "dest"
resume the state of executing processes captured in step 1 in "dest"
Assumption:
"src" is... (3 Replies)
Geeks,
Could you please help me out in my script and identify the missing piece. I need to check/get the exit status of a remote command executed on remote host through script and send out an email when process/processes is/are not running on any/all server(s).
Here's the complete... (5 Replies)
Discussion started by: lovesaikrishna
5 Replies
LEARN ABOUT V7
rexec
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)