1 .\" Copyright (c) 1983, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)rmt.8 8.3 (Berkeley) 6/1/94
35 .Nd remote magtape protocol module
41 utility is used by the remote dump and restore programs
42 in manipulating a magnetic tape drive through an interprocess
43 communication connection.
44 It is normally started up with an
50 utility accepts requests specific to the manipulation of
51 magnetic tapes, performs the commands, then responds with
57 Successful commands have responses of:
58 .Bd -ragged -offset indent
60 .Sy A Ar number No \en
67 representation of a decimal number.
68 Unsuccessful commands are responded to with:
69 .Bd -ragged -offset indent
71 .Xo Sy E Ar error-number
72 .No \en Ar error-message
79 is one of the possible error
84 is the corresponding error string as printed
87 The protocol is comprised of the
88 following commands, which are sent as indicated - no spaces are supplied
89 between the command and its arguments, or between its arguments, and
91 indicates that a newline should be supplied:
94 .It Xo Sy \&O Ar device
95 .No \en Ar mode No \en
103 is a full pathname and
107 representation of a decimal
108 number suitable for passing to
110 If a device had already been opened, it is
111 closed before a new open is performed.
113 .It Xo Sy C Ar device No \en
116 Close the currently open device.
119 specified is ignored.
128 operation using the specified parameters.
129 The response value is that returned from the
133 .It Sy W Ar count No \en
135 Write data onto the open device.
140 bytes from the connection, aborting if
141 a premature end-of-file is encountered.
142 The response value is that returned from
147 .It Sy R Ar count No \en
151 bytes of data from the open device.
154 exceeds the size of the data buffer (10 kilobytes), it is
155 truncated to the data buffer size.
158 utility then performs the requested
162 .Sy A Ar count-read No \en
165 successful; otherwise an error in the
166 standard format is returned.
168 was successful, the data read is then sent.
170 .It Xo Sy I Ar operation
171 .No \en Ar count No \en
177 command using the specified parameters.
178 The parameters are interpreted as the
180 representations of the decimal values
185 fields of the structure used in the
188 The return value is the
190 parameter when the operation is successful.
192 Return the status of the open device, as
197 If the operation was successful,
198 an ``ack'' is sent with the size of the
199 status buffer, then the status buffer is
203 Any other command causes
207 All responses are of the form described above.
219 People should be discouraged from using this for a remote
220 file access protocol.