hi everyone , i have a rsh problem , some of the users letf a lot of rsh sesions opened , i need a script that chek with a "ps -fea | grep rsh" and kill every sesion that not start today . for example
i already do , but manual can anyone help me with that
pd: sorry for my english
Last edited by Yogesh Sawant; 04-22-2008 at 04:58 AM..
Reason: added code tags
Hi All,
I want to execute a command from my Windows machine to Linux machine.
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 entered the... (1 Reply)
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)
Hi,
I issue :
rsh ****.16.0.151 -l root ls -l /tmp
and I receive :
connect to address ***.16.0.151: Connection refused
Trying krb4 rsh...
In hosts file of remote (***.16.0.151) I have :
***.16.0.202 root
Can you help me ?
Thank you. (0 Replies)
Hi
I have written a code that will exhaust the memory completely by allocating it and not freeing it. The OOM killer as expected in invoked and it killed a few high memory using processes and their childs.
But after that, though the system is not getting hung, it is not printing any msgs in... (3 Replies)
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
LEARN ABOUT OSX
rsh
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