|CU(1)||General Commands Manual||CU(1)|
cuis used to connect to another system over a serial link. In the era before modern networks, it was typically used to connect to a modem in order to dial in to a remote host. It is now frequently used for tasks such as attaching to the serial console of another machine for administrative or debugging purposes. The options are as follows:
cushould not allow the driver to block waiting for a carrier to be detected.
cuin restricted mode. This prevents all local filesystem operations (
~>) and command executions (
cuuses the remote(5) database to retrieve the dc (directly connected), dv (device) and br (baud rate) capabilities for that host. The
cuutility ignores other capabilities found in that database. Typed characters are normally transmitted directly to the remote machine (which does the echoing as well). A tilde (‘
~’) appearing as the first character of a line is an escape signal; the following are recognized:
cuprompts for the name of a local file to transmit.
BREAKto the remote system.
cu(only available with job control).
0 <-> remote tty in 1 <-> remote tty out 2 <-> local tty stderr
cuprompts for an argument, for example during setup of a file transfer, the line typed may be edited with the standard erase and kill characters. A null line in response to a prompt, or an interrupt, will abort the dialogue and return the user to the remote machine.
cuguards against multiple users connecting to a remote system by opening modems and terminal lines with exclusive access.
cuutility exits 0 on success, and >0 if an error occurs. remote(5)
cucommand appeared in 4.2BSD. This version was written for OpenBSD 5.4 by Nicholas Marriott.
|August 5, 2018||OpenBSD-current|