|
|
1.1 root 1: .\" Copyright (c) 1980 Regents of the University of California.
2: .\" All rights reserved. The Berkeley software License Agreement
3: .\" specifies the terms and conditions for redistribution.
4: .\"
5: .\" @(#)tip.1c 6.3 (Berkeley) 5/5/86
6: .\"
7: .TH TIP 1C "May 5, 1986"
8: .UC 4
9: .SH NAME
10: tip, cu \- connect to a remote system
11: .SH SYNOPSIS
12: .B tip
13: [
14: .B \-v
15: ] [
16: .BI \- speed
17: ] system-name
18: .br
19: .B tip
20: [
21: .B \-v
22: ] [
23: .BI \- speed
24: ] phone-number
25: .br
26: .B cu
27: phone-number
28: [
29: .B \-t
30: ] [
31: .B \-s
32: .I speed
33: ] [
34: .B \ -a
35: .I acu
36: ] [
37: .B \-l
38: .I line
39: ] [
40: .B \-#
41: ]
42: .SH DESCRIPTION
43: .I Tip
44: and
45: .I cu
46: establish a full-duplex connection to another machine,
47: giving the appearance of being logged in directly on the
48: remote cpu. It goes without saying that you must have a login
49: on the machine (or equivalent) to which you wish to connect.
50: The preferred interface is
51: .IR tip .
52: The
53: .I cu
54: interface is included for those people attached to the
55: ``call UNIX'' command of version 7. This manual page
56: describes only
57: .IR tip .
58: .PP
59: Typed characters are normally transmitted directly to the remote
60: machine (which does the echoing as well). A tilde (`~') appearing
61: as the first character of a line is an escape signal; the following
62: are recognized:
63: .TP 10
64: .B ~^D ~.
65: Drop the connection and exit
66: (you may still be logged in on the
67: remote machine).
68: .TP 10
69: \fB~c \fP [\fIname\fP]
70: Change directory to name (no argument
71: implies change to your home directory).
72: .TP 10
73: .B ~!
74: Escape to a shell (exiting the shell will
75: return you to tip).
76: .TP 10
77: .B ~>
78: Copy file from local to remote.
79: .I Tip
80: prompts for the name of a local file to transmit.
81: .TP 10
82: .B ~<
83: Copy file from remote to local.
84: .I Tip
85: prompts first for the name of the file to be sent, then for
86: a command to be executed on the remote machine.
87: .TP 10
88: \fB~p\fP \fIfrom\fP [ \fIto\fP ]
89: Send a file to a remote UNIX host. The put command causes the remote UNIX
90: system to run the command string ``cat > 'to''', while
91: .I tip
92: sends it the ``from''
93: file. If the ``to'' file isn't specified the ``from'' file name is used.
94: This command is actually a UNIX specific version of the ``~>'' command.
95: .TP 10
96: \fB~t\fP \fIfrom\fP [ \fIto\fP ]
97: Take a file from a remote UNIX host.
98: As in the put command the ``to'' file
99: defaults to the ``from'' file name if it isn't specified.
100: The remote host
101: executes the command string ``cat 'from';echo ^A'' to send the file to
102: .IR tip .
103: .TP 10
104: .B ~|
105: Pipe the output from a remote command to a local UNIX process.
106: The command string sent to the local UNIX system is processed by the shell.
107: .TP 10
108: .B ~$
109: Pipe the output from a local UNIX process to the remote host.
110: The command string sent to the local UNIX system is processed by the shell.
111: .TP 10
112: .B ~#
113: Send a BREAK to the remote system.
114: For systems which don't support the
115: necessary
116: .I ioctl
117: call the break is simulated by a sequence of line speed changes
118: and DEL characters.
119: .TP 10
120: .B ~s
121: Set a variable (see the discussion below).
122: .TP 10
123: .B ~^Z
124: Stop
125: .I tip
126: (only available with job control).
127: .TP 10
128: .B ~^Y
129: Stop only the ``local side'' of
130: .I tip
131: (only available with job control);
132: the ``remote side'' of
133: .IR tip ,
134: the side that displays output from the remote host, is left running.
135: .TP 10
136: .B ~?
137: Get a summary of the tilde escapes
138: .sp
139: .PP
140: .I Tip
141: uses the file /etc/remote to find how to reach a particular
142: system and to find out how it should operate while talking
143: to the system;
144: refer to
145: .IR remote (5)
146: for a full description.
147: Each system has a default baud rate with which to
148: establish a connection. If this value is not suitable, the baud rate
149: to be used may be specified on the command line, e.g. ``tip -300 mds''.
150: .PP
151: When
152: .I tip
153: establishes a connection it sends out a
154: connection message to the remote system; the default value, if any,
155: is defined in /etc/remote.
156: .PP
157: When
158: .I tip
159: prompts for an argument (e.g. during setup of
160: a file transfer) the line typed may be edited with the standard
161: erase and kill characters. A null line in response to a prompt,
162: or an interrupt, will abort the dialogue and return you to the
163: remote machine.
164: .PP
165: .I Tip
166: guards against multiple users connecting to a remote system
167: by opening modems and terminal lines with exclusive access,
168: and by honoring the locking protocol used by
169: .IR uucp (1C).
170: .PP
171: During file transfers
172: .I tip
173: provides a running count of the number of lines transferred.
174: When using the ~> and ~< commands, the ``eofread'' and ``eofwrite''
175: variables are used to recognize end-of-file when reading, and
176: specify end-of-file when writing (see below). File transfers
177: normally depend on tandem mode for flow control. If the remote
178: system does not support tandem mode, ``echocheck'' may be set
179: to indicate
180: .I tip
181: should synchronize with the remote system on the echo of each
182: transmitted character.
183: .PP
184: When
185: .I tip
186: must dial a phone number to connect to a system it will print
187: various messages indicating its actions.
188: .I Tip
189: supports the DEC DN-11 and Racal-Vadic 831 auto-call-units;
190: the DEC DF02 and DF03, Ventel 212+, Racal-Vadic 3451, and
191: Bizcomp 1031 and 1032 integral call unit/modems.
192: .PP
193: .SM
194: .B VARIABLES
195: .PP
196: .I Tip
197: maintains a set of
198: .I variables
199: which control its operation.
200: Some of these variable are read-only to normal users (root is allowed
201: to change anything of interest). Variables may be displayed
202: and set through the ``s'' escape. The syntax for variables is patterned
203: after
204: .IR vi (1)
205: and
206: .IR Mail (1).
207: Supplying ``all''
208: as an argument to the set command displays all variables readable by
209: the user. Alternatively, the user may request display of a particular
210: variable by attaching a `?' to the end. For example ``escape?''
211: displays the current escape character.
212: .PP
213: Variables are numeric, string, character, or boolean values. Boolean
214: variables are set merely by specifying their name; they may be reset
215: by prepending a `!' to the name. Other variable types are set by
216: concatenating an `=' and the value. The entire assignment must not
217: have any blanks in it. A single set command may be used to interrogate
218: as well as set a number of variables.
219: Variables may be initialized at run time by placing set commands
220: (without the ``~s'' prefix in a file
221: .I .tiprc
222: in one's home directory). The
223: .B \-v
224: option causes
225: .I tip
226: to display the sets as they are made.
227: Certain common variables have abbreviations.
228: The following is a list of common variables,
229: their abbreviations, and their default values.
230: .TP
231: .B beautify
232: .br
233: (bool) Discard unprintable characters when a session is being scripted;
234: abbreviated
235: .IR be .
236: .TP
237: .B baudrate
238: .br
239: (num) The baud rate at which the connection was established;
240: abbreviated
241: .IR ba .
242: .TP
243: .B dialtimeout
244: .br
245: (num) When dialing a phone number, the time (in seconds)
246: to wait for a connection to be established; abbreviated
247: .IR dial .
248: .TP
249: .B echocheck
250: .br
251: (bool) Synchronize with the remote host during file transfer by
252: waiting for the echo of the last character transmitted; default is
253: .IR off .
254: .TP
255: .B eofread
256: .br
257: (str) The set of characters which signify and end-of-tranmission
258: during a ~< file transfer command; abbreviated
259: .IR eofr .
260: .TP
261: .B eofwrite
262: .br
263: (str) The string sent to indicate end-of-transmission during
264: a ~> file transfer command; abbreviated
265: .IR eofw .
266: .TP
267: .B eol
268: .br
269: (str) The set of characters which indicate an end-of-line.
270: .I Tip
271: will recognize escape characters only after an end-of-line.
272: .TP
273: .B escape
274: .br
275: (char) The command prefix (escape) character; abbreviated
276: .IR es ;
277: default value is `~'.
278: .TP
279: .B exceptions
280: .br
281: (str) The set of characters which should not be discarded
282: due to the beautification switch; abbreviated
283: .IR ex ;
284: default value is ``\et\en\ef\eb''.
285: .TP
286: .B force
287: .br
288: (char) The character used to force literal data transmission;
289: abbreviated
290: .IR fo ;
291: default value is `^P'.
292: .TP
293: .B framesize
294: .br
295: (num) The amount of data (in bytes) to buffer between file system
296: writes when receiving files; abbreviated
297: .IR fr .
298: .TP
299: .B host
300: .br
301: (str) The name of the host to which you are connected; abbreviated
302: .IR ho .
303: .TP
304: .B prompt
305: .br
306: (char) The character which indicates and end-of-line on the remote
307: host; abbreviated
308: .IR pr ;
309: default value is `\en'. This value is used to synchronize during
310: data transfers. The count of lines transferred during a file transfer
311: command is based on recipt of this character.
312: .TP
313: .B raise
314: .br
315: (bool) Upper case mapping mode; abbreviated
316: .IR ra ;
317: default value is
318: .IR off .
319: When this mode is enabled, all lower case letters will be mapped to
320: upper case by
321: .I tip
322: for transmission to the remote machine.
323: .TP
324: .B raisechar
325: .br
326: (char) The input character used to toggle upper case mapping mode;
327: abbreviated
328: .IR rc ;
329: default value is `^A'.
330: .TP
331: .B record
332: .br
333: (str) The name of the file in which a session script is recorded;
334: abbreviated
335: .IR rec ;
336: default value is ``tip.record''.
337: .TP
338: .B script
339: .br
340: (bool) Session scripting mode; abbreviated
341: .IR sc ;
342: default is
343: .IR off .
344: When
345: .I script
346: is
347: .IR true ,
348: .I tip
349: will record everything transmitted by the remote machine in
350: the script record file specified in
351: .IR record .
352: If the
353: .I beautify
354: switch is on, only printable ASCII characters will be included in
355: the script file (those characters betwee 040 and 0177). The
356: variable
357: .I exceptions
358: is used to indicate characters which are an exception to the normal
359: beautification rules.
360: .TP
361: .B tabexpand
362: .br
363: (bool) Expand tabs to spaces during file transfers; abbreviated
364: .IR tab ;
365: default value is
366: .IR false .
367: Each tab is expanded to 8 spaces.
368: .TP
369: .B verbose
370: .br
371: (bool) Verbose mode; abbreviated
372: .IR verb ;
373: default is
374: .IR true .
375: When verbose mode is enabled,
376: .I tip
377: prints messages while dialing, shows the current number
378: of lines transferred during a file transfer operations,
379: and more.
380: .TP
381: .B SHELL
382: .br
383: (str) The name of the shell to use for the ~! command; default
384: value is ``/bin/sh'', or taken from the environment.
385: .TP
386: .B HOME
387: .br
388: (str) The home directory to use for the ~c command; default
389: value is taken from the environment.
390: .PP
391: .SH FILES
392: .ta \w'/usr/spool/uucp/LCK..* 'u
393: .nf
394: /etc/remote global system descriptions
395: /etc/phones global phone number data base
396: ${REMOTE} private system descriptions
397: ${PHONES} private phone numbers
398: ~/.tiprc initialization file.
399: /usr/spool/uucp/LCK..* lock file to avoid conflicts with \fIuucp\fP
400: .fi
401: .SH DIAGNOSTICS
402: Diagnostics are, hopefully, self explanatory.
403: .SH "SEE ALSO"
404: remote(5),
405: phones(5)
406: .SH BUGS
407: The full set of variables is undocumented and should, probably, be
408: paired down.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.