cu(1c) [v7 man page]

CU(1C)																	    CU(1C)

NAME

       cu - call UNIX

SYNOPSIS

       cu telno [ -t ] [ -s speed ] [ -a acu ] [ -l line ]

DESCRIPTION

       Cu calls up another UNIX system, a terminal, or possibly a non-UNIX system.  It manages an interactive conversation with possible transfers
       of text files.  Telno is the telephone number, with minus signs at appropriate places for delays.  The -t flag is used to  dial	out  to  a
       terminal.  Speed gives the transmission speed (110, 134, 150, 300, 1200); 300 is the default value.

       The  -a	and -l values may be used to specify pathnames for the ACU and communications line devices.  They can be used to override the fol-
       lowing built-in choices:

       -a /dev/cua0 -l /dev/cul0

       After making the connection, cu runs as two processes: the send process reads the standard input and passes most of it to the  remote  sys-
       tem;  the  receive process reads from the remote system and passes most data to the standard output.  Lines beginning with `~' have special
       meanings.

       The send process interprets the following:

       ~.		 terminate the conversation.
       ~EOT		 terminate the conversation

       ~<file		 send the contents of file to the remote system, as though typed at the terminal.

       ~!		 invoke an interactive shell on the local system.

       ~!cmd ...	 run the command on the local system (via sh -c).

       ~$cmd ...	 run the command locally and send its output to the remote system.

       ~%take from [to]  copy file `from' (on the remote system) to file `to' on the local system.  If `to' is omitted, the `from'  name  is  used
			 both places.

       ~%put from [to]	 copy  file  `from'  (on  local  system)  to file `to' on remote system.  If `to' is omitted, the `from' name is used both
			 places.

       ~~...		 send the line `~...'.

       The receive process handles output diversions of the following form:

       ~>[>][:]file
       zero or more lines to be written to file
       ~>

       In any case, output is diverted (or appended, if `>>' used) to the file.  If `:' is used, the diversion is silent, i.e., it is written only
       to  the	file.	If `:' is omitted, output is written both to the file and to the standard output.  The trailing `~>' terminates the diver-
       sion.

       The use of ~%put requires stty and cat on the remote side.  It also requires that the current erase and kill characters on the remote  sys-
       tem be identical to the current ones on the local system.  Backslashes are inserted at appropriate places.

       The  use  of  ~%take requires the existence of echo and tee on the remote system.  Also, stty tabs mode is required on the remote system if
       tabs are to be copied without expansion.

FILES

       /dev/cua0
       /dev/cul0
       /dev/null

SEE ALSO

       dn(4), tty(4)

DIAGNOSTICS

       Exit code is zero for normal exit, nonzero (various values) otherwise.

BUGS

       The syntax is unique.

																	    CU(1C)

Check Out this Related Man Page

RSH(1C) 																   RSH(1C)

NAME

       rsh - remote shell

SYNOPSIS

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

DESCRIPTION

       Rsh  connects to the specified host, and executes the specified command.  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  remote  username  used is the same as your local username, unless you specify a different remote name with the -l option.  This remote
       name must be equivalent (in the sense of rlogin(1C)) to the originating account; no provision is made for specifying a password with a com-
       mand.

       If you omit command, then instead of executing a single command, you will be logged in on the remote host using rlogin(1C).

       Shell  metacharacters  which  are  not  quoted  are interpreted on local machine, while quoted metacharacters are interpreted on the remote
       machine.  Thus the command

	  rsh otherhost cat remotefile >> localfile

       appends the remote file remotefile to the localfile localfile, while

	  rsh otherhost cat remotefile ">>" otherremotefile

       appends remotefile to otherremotefile.

       Host names are given in the file /etc/hosts.  Each host has one standard name (the first name given in the file), which is rather long  and
       unambiguous, and optionally one or more nicknames.  The host names for local machines are also commands in the directory /usr/hosts; if you
       put this directory in your search path then the rsh can be omitted.

FILES

       /etc/hosts
       /usr/hosts/*

SEE ALSO

       rlogin(1C)

BUGS

       If you are using csh(1) and put a rsh(1C) 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)); use rlogin(1C).

       Stop  signals  stop  the  local	rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain
       here.

4.2 Berkeley Distribution					  April 29, 1985							   RSH(1C)

Linux and UNIX Man Pages

cu(1c) [v7 man page]

Check Out this Related Man Page