Web Hosting Directory | Web Hosting Resources | Webmaster Resources | Domain Tools | Search Engine Marketing | Forums
  Signup
Today: 893   Yesterday: 1,172   Max: 1,872   Total: 384,274   Current Users : 20 (Member 0) 
DOMAIN TOOLS

WEBMASTER TOOLS

RELATED ARTICLES

SUBMIT AN ARTICLE

Write for us and get publicity, link to your website, and best of all get paid. Please visit our writers page for details.


LINK TO US

Link to us and earn points for each visitor you bring to us. Please visit our link partner page for details.

 
Search Linux manpages For:  

rsh(1) -- Linux man page

 

NAME

rsh - remote shell  

SYNOPSIS

rsh [-Kdnx ] [-l username ] host [command]  

DESCRIPTION

Rsh executes command on host

Rsh 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:

-d
The -d option turns on socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host.
-l
By default, the remote username is the same as the local username. The -l option allows the remote name to be specified.
-n
The -n option redirects input from the special device /dev/null (see the Sx BUGS section of this manual page).

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),  

HISTORY

The rsh command appeared in BSD 4.2  

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 rogue(6) 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.


 
 
What is your major source of website traffic?
 
 
 
 
 
 

ADVERTISEMENT

 
Cheap Web HostingBudget Web HostingEcommerce Web Hosting
Link to UsLink ExchangeAdvertisePrivacy PolicyTerms Of ServiceAbout UsContact UsSitemap
Copyright © 2006 - 2008 Broadband Media, Inc. All rights reserved.