Lines Matching full:remote

70 is run refer to the remote connection.
89 generated for data sent to the remote system.
109 Ignores one hangup. This allows the user to remain in \fBcu\fR while the remote
114 dialback configuration, see \fBremote\fR(4) and \fISystem Administration Guide:
169 generated for data sent to the remote system.
231 information for connecting to remote systems, but it is not generally readable.
299 connection to the remote machine, then there is no need to specify a
310 \fB~\fR, passes it to the remote system. The \fBreceive\fR process accepts data
311 from the remote system and, except for lines beginning with \fB~\fR, passes it
313 control input from the remote so the buffer is not overrun. Lines beginning
352 Runs \fIcmd\fR locally and send its output to the remote system.
371 Copies file \fIfrom\fR (on the remote system) to file \fIto\fR on the local
381 Copies file \fIfrom\fR (on local system) to file \fIto\fR on remote system. If
391 Sends the line \fB~\fR \fIline\fR to the remote system.
400 Transmits a  \fBBREAK\fR to the remote system (which can also be specified as
430 Prints the values of the termio structure variables for the remote
441 useful when the remote system does not respond properly to the DC3 and DC1
452 flow controlled by the remote host (can also be specified as
486 The \fBreceive\fR process normally copies data from the remote system to the
491 The use of \fB~%put\fR requires \fBstty\fR(1) and \fBcat\fR(1) on the remote
492 side. It also requires that the current erase and kill characters on the remote
498 \fBcat\fR(1) on the remote system, and that the remote system must be using the
500 on the remote system if tabs are to be copied without expansion to spaces.
668 \fBct\fR(1C), \fBuuname\fR(1C), \fBuucp\fR(1C), \fBremote\fR(4),
693 Forward to the remote system.
702 Forward to the remote system.