xref: /386bsd/usr/share/man/cat1/cu.0 (revision a2142627)
1TIP(1)                      386BSD Reference Manual                     TIP(1)
2
3NNAAMMEE
4     ttiipp, ccuu - connect to a remote system
5
6SSYYNNOOPPSSIISS
7     ttiipp [--vv] --_s_p_e_e_d _s_y_s_t_e_m-_n_a_m_e
8     ttiipp [--vv] --_s_p_e_e_d _p_h_o_n_e-_n_u_m_b_e_r
9     ccuu _p_h_o_n_e-_n_u_m_b_e_r [--tt] [--ss _s_p_e_e_d] [--aa _a_c_u] [--ll _l_i_n_e] [--##]
10
11DDEESSCCRRIIPPTTIIOONN
12     TTiipp and _c_u establish a full-duplex connection to another machine, giving
13     the appearance of being logged in directly on the remote cpu.  It goes
14     without saying that you must have a login on the machine (or equivalent)
15     to which you wish to connect.  The preferred interface is ttiipp. The _c_u
16     interface is included for those people attached to the ``call UNIX''
17     command of version 7.  This manual page describes only ttiipp.
18
19     Available Option:
20
21     --vv      Set verbose mode.
22
23     Typed characters are normally transmitted directly to the remote machine
24     (which does the echoing as well).  A tilde (`~') appearing as the first
25     character of a line is an escape signal; the following are recognized:
26
27     ~~^^DD or ~~.
28           Drop the connection and exit (you may still be logged in on the
29           remote machine).
30
31     ~~cc [_n_a_m_e]
32           Change directory to _n_a_m_e (no argument implies change to your home
33           directory).
34
35     ~~!!    Escape to a shell (exiting the shell will return you to tip).
36
37     ~~>>    Copy file from local to remote.  TTiipp prompts for the name of a
38           local file to transmit.
39
40     ~~<<    Copy file from remote to local.  TTiipp prompts first for the name of
41           the file to be sent, then for a command to be executed on the
42           remote machine.
43
44     ~~pp _f_r_o_m [_t_o]
45           Send a file to a remote UNIX host.  The put command causes the
46           remote UNIX system to run the command string ``cat > 'to''', while
47           ttiipp sends it the ``from'' file.  If the ``to'' file isn't specified
48           the ``from'' file name is used.  This command is actually a UNIX
49           specific version of the ``~>'' command.
50
51     ~~tt _f_r_o_m [_t_o]
52           Take a file from a remote UNIX host.  As in the put command the
53           ``to'' file defaults to the ``from'' file name if it isn't
54           specified.  The remote host executes the command string ``cat
55           'from';echo ^A'' to send the file to ttiipp.
56
57     ~~     Pipe the output from a remote command to a local UNIX process.  The
58           command string sent to the local UNIX system is processed by the
59           shell.
60
61     ~~$$    Pipe the output from a local UNIX process to the remote host.  The
62           command string sent to the local UNIX system is processed by the
63           shell.
64
65     ~~##    Send a BREAK to the remote system.  For systems which don't support
66           the necessary _i_o_c_t_l call the break is simulated by a sequence of
67           line speed changes and DEL characters.
68
69     ~~ss    Set a variable (see the discussion below).
70
71     ~~^^ZZ   Stop ttiipp (only available with job control).
72
73     ~~^^YY   Stop only the ``local side'' of ttiipp (only available with job
74           control); the ``remote side'' of ttiipp, the side that displays output
75           from the remote host, is left running.
76
77     ~~??    Get a summary of the tilde escapes
78
79     TTiipp uses the file /_e_t_c/_r_e_m_o_t_e to find how to reach a particular system
80     and to find out how it should operate while talking to the system; refer
81     to remote(5) for a full description.  Each system has a default baud rate
82     with which to establish a connection.  If this value is not suitable, the
83     baud rate to be used may be specified on the command line, e.g.  `tip
84     -300 mds'.
85
86     When ttiipp establishes a connection it sends out a connection message to
87     the remote system; the default value, if any, is defined in /_e_t_c/_r_e_m_o_t_e
88     (see remote(5)).
89
90     When ttiipp prompts for an argument (e.g. during setup of a file transfer)
91     the line typed may be edited with the standard erase and kill characters.
92     A null line in response to a prompt, or an interrupt, will abort the
93     dialogue and return you to the remote machine.
94
95     TTiipp guards against multiple users connecting to a remote system by
96     opening modems and terminal lines with exclusive access, and by honoring
97     the locking protocol used by uucp(1).
98
99     During file transfers ttiipp provides a running count of the number of lines
100     transferred.  When using the ~> and ~< commands, the ``eofread'' and
101     ``eofwrite'' variables are used to recognize end-of-file when reading,
102     and specify end-of-file when writing (see below).  File transfers
103     normally depend on tandem mode for flow control.  If the remote system
104     does not support tandem mode, ``echocheck'' may be set to indicate ttiipp
105     should synchronize with the remote system on the echo of each transmitted
106     character.
107
108     When ttiipp must dial a phone number to connect to a system it will print
109     various messages indicating its actions.  TTiipp supports the DEC DN Ns-11
110     and Racal-Vadic 831 auto-call-units; the DEC DF02 and DF03, Ventel 212+,
111     Racal-Vadic 3451, and Bizcomp 1031 and 1032 integral call unit/modems.
112
113   VVAARRIIAABBLLEESS
114     TTiipp maintains a set of _v_a_r_i_a_b_l_e_s which control its operation.  Some of
115     these variable are read-only to normal users (root is allowed to change
116     anything of interest).  Variables may be displayed and set through the
117     ``s'' escape.  The syntax for variables is patterned after vi(1) and
118     Mail(1).  Supplying ``all'' as an argument to the set command displays
119     all variables readable by the user.  Alternatively, the user may request
120     display of a particular variable by attaching a `?' to the end.  For
121     example ``escape?''  displays the current escape character.
122
123     Variables are numeric, string, character, or boolean values.  Boolean
124     variables are set merely by specifying their name; they may be reset by
125     prepending a `!' to the name.  Other variable types are set by
126     concatenating an `=' and the value.  The entire assignment must not have
127     any blanks in it.  A single set command may be used to interrogate as
128     well as set a number of variables.  Variables may be initialized at run
129     time by placing set commands (without the ``~s'' prefix in a file ._t_i_p_r_c
130     in one's home directory).  The --vv option causes ttiipp to display the sets
131     as they are made.  Certain common variables have abbreviations.  The
132     following is a list of common variables, their abbreviations, and their
133     default values.
134
135     _b_e_a_u_t_i_f_y      (bool) Discard unprintable characters when a session is
136                   being scripted; abbreviated _b_e.
137
138     _b_a_u_d_r_a_t_e      (num) The baud rate at which the connection was
139                   established; abbreviated _b_a.
140
141     _d_i_a_l_t_i_m_e_o_u_t   (num) When dialing a phone number, the time (in seconds) to
142                   wait for a connection to be established; abbreviated _d_i_a_l.
143
144     _e_c_h_o_c_h_e_c_k     (bool) Synchronize with the remote host during file
145                   transfer by waiting for the echo of the last character
146                   transmitted; default is _o_f_f.
147
148     _e_o_f_r_e_a_d       (str) The set of characters which signify and end-of-
149                   tranmission during a ~< file transfer command; abbreviated
150                   _e_o_f_r.
151
152     _e_o_f_w_r_i_t_e      (str) The string sent to indicate end-of-transmission
153                   during a ~> file transfer command; abbreviated _e_o_f_w.
154
155     _e_o_l           (str) The set of characters which indicate an end-of-line.
156                   TTiipp will recognize escape characters only after an end-of-
157                   line.
158
159     _e_s_c_a_p_e        (char) The command prefix (escape) character; abbreviated
160                   _e_s; default value is `~'.
161
162     _e_x_c_e_p_t_i_o_n_s    (str) The set of characters which should not be discarded
163                   due to the beautification switch; abbreviated _e_x; default
164                   value is ``\t\n\f\b''.
165
166     _f_o_r_c_e         (char) The character used to force literal data
167                   transmission; abbreviated _f_o; default value is `^P'.
168
169     _f_r_a_m_e_s_i_z_e     (num) The amount of data (in bytes) to buffer between file
170                   system writes when receiving files; abbreviated _f_r.
171
172     _h_o_s_t          (str) The name of the host to which you are connected;
173                   abbreviated _h_o.
174
175     _p_r_o_m_p_t        (char) The character which indicates and end-of-line on the
176                   remote host; abbreviated _p_r; default value is `\n'.  This
177                   value is used to synchronize during data transfers.  The
178                   count of lines transferred during a file transfer command
179                   is based on recipt of this character.
180
181     _r_a_i_s_e         (bool) Upper case mapping mode; abbreviated _r_a; default
182                   value is _o_f_f. When this mode is enabled, all lower case
183                   letters will be mapped to upper case by ttiipp for
184                   transmission to the remote machine.
185
186     _r_a_i_s_e_c_h_a_r     (char) The input character used to toggle upper case
187                   mapping mode; abbreviated _r_c; default value is `^A'.
188
189     _r_e_c_o_r_d        (str) The name of the file in which a session script is
190                   recorded; abbreviated _r_e_c; default value is ``tip.record''.
191
192     _s_c_r_i_p_t        (bool) Session scripting mode; abbreviated _s_c; default is
193                   _o_f_f. When _s_c_r_i_p_t is true, ttiipp will record everything
194                   transmitted by the remote machine in the script record file
195                   specified in _r_e_c_o_r_d. If the _b_e_a_u_t_i_f_y switch is on, only
196                   printable ASCII characters will be included in the script
197                   file (those characters betwee 040 and 0177).  The variable
198                   _e_x_c_e_p_t_i_o_n_s is used to indicate characters which are an
199                   exception to the normal beautification rules.
200
201     _t_a_b_e_x_p_a_n_d     (bool) Expand tabs to spaces during file transfers;
202                   abbreviated _t_a_b; default value is _f_a_l_s_e. Each tab is
203                   expanded to 8 spaces.
204
205     _v_e_r_b_o_s_e       (bool) Verbose mode; abbreviated _v_e_r_b; default is _t_r_u_e.
206                   When verbose mode is enabled, ttiipp prints messages while
207                   dialing, shows the current number of lines transferred
208                   during a file transfer operations, and more.
209
210EENNVVIIRROONNMMEENNTT
211     TTiipp uses the following environment variables:
212
213     SHELL       (str) The name of the shell to use for the ~! command;
214                 default value is ``/bin/sh'', or taken from the environment.
215
216     HOME        (str) The home directory to use for the ~c command; default
217                 value is taken from the environment.
218
219     HOST        Check for a default host if none specified.
220
221     The variables ${REMOTE} and ${PHONES} are also exported.
222
223FFIILLEESS
224     /etc/remote             Global system descriptions.
225     /etc/phones             Global phone number data base.
226     ${REMOTE}               Private system descriptions.
227     ${PHONES}               Private phone numbers.
228     ~/.tiprc                Initialization file.
229     tip.record              Record file.
230     /var/log/aculog         Line access log.
231     /var/spool/uucp/LCK..*  Lock file to avoid conflicts with uucp.
232
233DDIIAAGGNNOOSSTTIICCSS
234     Diagnostics are, hopefully, self explanatory.
235
236SSEEEE AALLSSOO
237     remote(5),  phones(5)
238
239HHIISSTTOORRYY
240     The ttiipp appeared command in 4.2BSD.
241
242BBUUGGSS
243     The full set of variables is undocumented and should, probably, be paired
244     down.
245
2464th Berkeley Distribution        July 27, 1991                               4
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265