07-29-2009
rsh fails with -n option
Issue is with rsh loggin.
I tried logging into solaris machine from solaris machine using rsh with login prompt, it passes.
$ rsh -l USERNAME IPADDRESS
<Prompt for password> :
USERNAME logged in .......
$
when i try same command with -n option(required for automation), it fails,
$ rsh -l USERNAME -n IPADDRESS
permission denied
$
".rhosts" file has 0777 permission and contains the correct entry..
Case 1 : Remote machine is Solaris 8 and machine executing rsh command is Solaris 6.
Case 2 : when i use remote machine as Solaris 10 and machine executing rsh command is Solaris 6, it is successfull.
Any ideas why it is failing at Case 1 ?? Basically why -n option is failing and is there any alternate option ??
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am trying to run a Perl script using rsh. I need to be able to capture the return code value, so the calling script can handle failures properly.
I cannot modify the Perl script I need to run because we use it for all of our servers.
Does anyone have a suggestion? (1 Reply)
Discussion started by: kscase
1 Replies
2. Shell Programming and Scripting
Hi,
i need to xecute rsh or rexec command in order to execute the script on multiple server.
The problem i am facing is when i execute rsh command with login name and hostname it ask me password interactively
can some body help me how i can pass password along with the command or how to... (1 Reply)
Discussion started by: deep022in
1 Replies
3. UNIX for Advanced & Expert Users
Hi All,
I want to execute a command from my Windows machine to Linux machine using RSH only
d:> rsh <Linux machine add> -l <user_name> pwd>dir
in linux machine users home directory in .rhosts file I entered the windows machine IP address and user name.
In linux etc/hosts.equiv file I... (1 Reply)
Discussion started by: sarwan
1 Replies
4. Shell Programming and Scripting
Hi all,
I am parsing command line options using getopts.
The problem is that mandatory argument options following ":" is taking next option as argument if it is not followed by any argument.
Below is the script:
while getopts :hd:t:s:l:p:f: opt
do
case "$opt" in
-h|-\?)... (2 Replies)
Discussion started by: gurukottur
2 Replies
5. AIX
How to configure rsh for different users in aix? (4 Replies)
Discussion started by: vjm
4 Replies
6. Solaris
How to enable rsh in solaris (7 Replies)
Discussion started by: durgaprasadr13
7 Replies
7. Shell Programming and Scripting
I have a script with several options and during testing I found that the \? option does not handle options without dashes as I would expect. Then I run the script with any option that does not include a dash, it runs the script when I would expect \? to catch it and error.
I've tried this with... (2 Replies)
Discussion started by: HexKnot
2 Replies
8. Shell Programming and Scripting
To find all the files in your home directory that have been edited in some way since the last tar file, use this command:
find . -newer backup.tar.gz
Is anyone familiar with an older solution?
looking to identify files older then 15mins across several directories.
thanks,
manny (2 Replies)
Discussion started by: mr_manny
2 Replies
9. Linux
Hi All,
Whenever we are giving rsh localhost date , it give an error "Permission Denied".
RHEL 6 is the version, and we're logging in as "root".
in .rhosts file I have mentioned all the details, and enabled rsh,rsync,rexec,rlogin in /etc/xinetd.d/ file
Please suggest.
Reg,
Muzaffar (7 Replies)
Discussion started by: muzaffar.k
7 Replies
10. Solaris
Hi,
I installed some packages required by an app built with python.
But when I try python setup.py install, I get the following error:
/opt/csw/lib/gcc/sparc-sun-solaris2.10/5.2.0/../../../../sparc-sun-solaris2.10/bin/as: unrecognized option `-m32'
Could anyone tell me what's wrong... (4 Replies)
Discussion started by: Kimkun
4 Replies
RSH(1) BSD General Commands Manual RSH(1)
NAME
rsh -- remote shell
SYNOPSIS
rsh [-46dn] [-l username] [-t timeout] host [command]
DESCRIPTION
The rsh utility executes command on host.
The rsh utility copies its standard input to the remote command, the standard output of the remote command to its standard output, and the
standard error of the remote command to its standard error. Interrupt, quit and terminate signals are propagated to the remote command; rsh
normally terminates when the remote command does. The options are as follows:
-4 Use IPv4 addresses only.
-6 Use IPv6 addresses only.
-d Turn on socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host.
-l username
Allow the remote username to be specified. By default, the remote username is the same as the local username. Authorization is deter-
mined as in rlogin(1).
-n Redirect input from the special device /dev/null (see the BUGS section of this manual page).
-t timeout
Allow a timeout to be specified (in seconds). If no data is sent or received in this time, rsh will exit.
If no command is specified, you will be logged in on the remote host using rlogin(1).
Shell metacharacters which are not quoted are interpreted on local machine, while quoted metacharacters are interpreted on the remote
machine. For example, the command
rsh otherhost cat remotefile >> localfile
appends the remote file remotefile to the local file localfile, while
rsh otherhost cat remotefile ">>" other_remotefile
appends remotefile to other_remotefile.
FILES
/etc/hosts
/etc/auth.conf
SEE ALSO
rlogin(1), setsockopt(2), rcmd(3), ruserok(3), auth.conf(5), hosts(5), hosts.equiv(5), rlogind(8), rshd(8)
HISTORY
The rsh command appeared in 4.2BSD.
BUGS
If you are using csh(1) and put a rsh in the background without redirecting its input away from the terminal, it will block even if no reads
are posted by the remote command. If no input is desired you should redirect the input of rsh to /dev/null using the -n option.
You cannot run an interactive command (like ee(1) or vi(1)) using rsh; use rlogin(1) instead.
Stop signals stop the local rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here.
BSD
October 16, 2002 BSD