06-04-2007
problem in rlogin
Dear Experts,
i want to make one script ,by running that script it should rlogin from one mashine to another and the username and passord should be in the script so that it could not ask from me the username and password of another machine from me .
please help me out.
Regards,
SHARY
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
From any computer on our network when you rlogin into one machine (this only happens on this machine) it'll hang for about 3 minutes before loggin into that machine. If your sick of waiting you can do a <ctrl> C and then it'll rlogin into the machine it is meant to BUT it wont keep the shell... (1 Reply)
Discussion started by: merlin
1 Replies
2. UNIX for Advanced & Expert Users
hi !
i ve a problem with rlogin. i have a server from which only root user can Rlogin other servers.
other users can t rlogin, they get the following error :
"rcmd2: socket: The file access permissions do not allow the specified action"
Does somebody can help ?
Thanks,
Karine (3 Replies)
Discussion started by: karine
3 Replies
3. Shell Programming and Scripting
I'm comparing a table from two databases on two different servers to check for equality.
1. How do I use rlogin from a script , is it like this ?
rlogin -l $username $server1
where $username and $server1 are passed from the command line.
2.create a copy of that table, compress it and... (3 Replies)
Discussion started by: seaten
3 Replies
4. Cybersecurity
does anyone know how to stop rlogin to my sunsolaris
so I have 2 machines...I can not telnet one becouse that is not allowed but I can telnet the other and do rlogin to first one..I want to stop that..
so..
telnet A from C machine - works
telnet B from C machine - does not work
but... (3 Replies)
Discussion started by: amon
3 Replies
5. IP Networking
On the HP-UX hostA, the command rlogin hostB generates the error "rlogind: Host address mismatch" even though the hostname & IP of hostA are defined in the .rhosts file and the /etc/hosts files of hostB respectively. The IP and the hostname of hostB are defined in the /etc/hosts file of hostA. (1 Reply)
Discussion started by: vijaysharma.vs
1 Replies
6. UNIX for Advanced & Expert Users
I need to establish rlogin between 2 of my servers (and I know, it's not secure, smart, etc. ... it's a temporary requirement that I have to do)
I tried all the standards.
I'm trying to rlogin from server A to server B
On server B, I made a /.rhosts file that contains server A's name
On... (4 Replies)
Discussion started by: FredSmith
4 Replies
7. HP-UX
on the system, sometimes the rlogin command can not login the remote node,but ping command can echo the packet. if the inetd domean restarted , rlogin runs normally. We want to know what cause the rlogin failed and how to fix it. (2 Replies)
Discussion started by: Frank2004
2 Replies
8. Shell Programming and Scripting
Hi all,
i need to remotely execute a couple of commands on anyother server, but rsh is not allowed. for that matter i am bound to use rlogin. so what i am trying to do in the script is :
1) rlogin asad
2) Wait for Login prompt
3) Waiting for Password Prompt
4) Once authenticated, execute... (4 Replies)
Discussion started by: asadlone
4 Replies
9. UNIX for Dummies Questions & Answers
Hi,
in my environment we have several server with rlogin passwordless login enabled, now there is a problem to setup this with a hpux server. i have check the .rhosts file and kerberos key are all setup properly and permission is correct, even other user id on the server can login without... (3 Replies)
Discussion started by: robertngo
3 Replies
10. UNIX for Dummies Questions & Answers
Hello,
When I try and RSH/RLOGIN onto a box with user root, I get the prompt but the username/password combination NEVER work. I have the password up properly on the host machine. Does rsh/rlogin not make use of ./etc/passwd and /etc/shadow? (1 Reply)
Discussion started by: mojoman
1 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
SEE ALSO
rlogin(1), setsockopt(2), rcmd(3), ruserok(3), 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