| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Other Berkeley Remote ("r") Commands (rcp, ruptime, rwho) The rlogin and rsh commands are the generic members of the Berkeley r family of programs that allow remote access to a host. To complement these, a small number of specific remote commands were also defined. These are essentially remote versions of some of the more common UNIX functionsinstead of the command being applied to only one system, however, it is used between two systems or across all systems on a TCP/IP network. All of these commands are based on rlogin the same way that rsh is. They work in the same way, but instead of opening up a session or passing a user-specified command to the remote host, they execute a particular function. The following are the most common of these remote commands and briefly, how each is used:
The ruptime and rwho commands both rely on the presence of the rwhod (remote who daemon) running in the background on networked machines. These processes routinely share information with each other about host uptime and who is logged on to each system, so it can be quickly displayed when either ruptime or rwho is run. On some operating systems, other remote commands may also be implemented. As with rlogin and rsh, security issues may apply to these commands, and there may be efficiency concerns with others (such as rwho). For these reasons, on many networks these commands are no longer used.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||