I am trying to enable rexec to automate certain tasks(it has to be rexec, not ssh or any other due to the system environment), so after switching to linux, I followed the certain instructions that were laid out in the web.
My operating system is fedora 17, so I first installed the rsh-server.i686 package(which includes rexec), enabled it from /etc/xinetd.d/rexec by changing it as the following :
I also edited /etc/pam.d/rexec and commented out the nologin line like this :
I've added + + in the .rhosts file for each user and also the /etc/hosts.equiv file(which will later be replaced by hostname/user, but for now, + + for testing purposes).
I also added rexec in /etc/securetty. Then I restarted xinetd. Just in case, I temporarily disabled SELinux and iptables also so nothing will get in the way.
I believe I followed all the right procedures in order to get rexec working, but when I issue the command, it seems to work but the output is plain blank :
The reason why I think it's partially working is because there is no delay when executing the command, and there is no error message.
But the result does not seem to output back to the host.
The port 512 is listening so the rexecd daemon seems to be working fine.
Does any know how to fix this?
Thanks!
Last edited by Scott; 10-25-2012 at 03:08 AM..
Reason: Code tags
Hello Again,
Those that have noticed my earlier posts will know that I have succesfully installed Solaris 8 onto my pc. I haven't been able to get x-server working (i think it doesn't like my video card) though I've been able to log into root (with a bit of help from unix forums :o ) and have... (2 Replies)
telnet at my system is behaving stange. Some times I am able to telnet to other machines but sometimes it stop doing that. Then i have to reboot the machine and most of the time (not 100%) it works. SImilar is the case with SSH. Sometime it works , some time it don't. i am new to Unix and I do not... (1 Reply)
Hi,
I do have three scripts. Whcih inserts records into a table using sqlldr, creating some reprot files etc. The first script will call the second and then the second will call the third. When I run my first script from the shell prompt, all my operation are completed successfully. If I do... (23 Replies)
Hi all,
I'm trying to generate a series of txt files starting from a plain csv file
part of my code:
#!/bin/ksh
INSTALLDIR=/Users/ME/Installdir
CSV=CSV.csv
TMP=/tmp/$(basename $0).txt
tr -s "\r" "\n" < /$INSTALLDIR/$CSV > $TMP
function Makefiles
{
printf '%24s:%30s\n' "sometext"... (1 Reply)
Hi All,
Can any one help me to solve the issue.
The Issue is, i have started the sendmail service on my RHEL 4 update 6 box, I am able to send the mail from my box to almost all of the Email Id's except few.
Exampe,
test mail.
.
Output is :the message is sent.
now if I send the... (2 Replies)
This is the first time for using sudo for me.
# visudo
## Allows people in group admin to run all commands
%admin ALL=(ALL) ALL
# groupadd admin
# useradd temp
# usermod -a -G admin temp
# id temp
uid=506(temp) gid=506(temp) groups=506(temp),507(admin)
#
#sudo... (5 Replies)
Hi There,
---------
file1
-------
~c asd@ac.com
--------------
Now i am using below command
cat file1|mailx -s " testing" -r " My Name" abc@tech.com (3 Replies)
I want to join two files , with file 1 col 3 and file 2 col 1 as key.
The join command is erratic for some reason. File 2 is a master file having all the names, and file 1 has some values. I want to add the names from fil2 in file 1. If I use the original master file, some output is missing.
... (16 Replies)
Discussion started by: ritakadm
16 Replies
LEARN ABOUT XFREE86
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)