The OpenNET Project / Index page

[ новости/++ | форум | wiki | теги ]

Интерактивная система просмотра системных руководств (man-ов)

 ТемаНаборКатегория 
 
 [Cписок руководств | Печать]

rsh (1)
  • rsh (1) ( Solaris man: Команды и прикладные программы пользовательского уровня )
  • rsh (1) ( FreeBSD man: Команды и прикладные программы пользовательского уровня )
  • rsh (1) ( Русские man: Команды и прикладные программы пользовательского уровня )
  • >> rsh (1) ( Linux man: Команды и прикладные программы пользовательского уровня )

  • BSD mandoc
    Linux NetKit (0.17)  

    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.


     

    Index

    NAME
    SYNOPSIS
    DESCRIPTION
    FILES
    SEE ALSO
    HISTORY
    BUGS


    Поиск по тексту MAN-ов: 




      Закладки на сайте
      Проследить за страницей
    Created 1996-2017 by Maxim Chirkov  
    ДобавитьРекламаВебмастеруГИД  
    Hosting by Ihor