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 .\" 4. 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
36 .Nd remote magtape protocol module
42 utility is used by the remote dump and restore programs
43 in manipulating a magnetic tape drive through an interprocess
44 communication connection.
45 It is normally started up with an
51 utility accepts requests specific to the manipulation of
52 magnetic tapes, performs the commands, then responds with
58 Successful commands have responses of:
59 .Bd -ragged -offset indent
61 .Sy A Ar number No \en
68 representation of a decimal number.
69 Unsuccessful commands are responded to with:
70 .Bd -ragged -offset indent
72 .Xo Sy E Ar error-number
73 .No \en Ar error-message
80 is one of the possible error
85 is the corresponding error string as printed
88 The protocol is comprised of the
89 following commands, which are sent as indicated - no spaces are supplied
90 between the command and its arguments, or between its arguments, and
92 indicates that a newline should be supplied:
95 .It Xo Sy \&O Ar device
96 .No \en Ar mode No \en
104 is a full pathname and
108 representation of a decimal
109 number suitable for passing to
111 If a device had already been opened, it is
112 closed before a new open is performed.
114 .It Xo Sy C Ar device No \en
117 Close the currently open device.
120 specified is ignored.
129 operation using the specified parameters.
130 The response value is that returned from the
134 .It Sy W Ar count No \en
136 Write data onto the open device.
141 bytes from the connection, aborting if
142 a premature end-of-file is encountered.
143 The response value is that returned from
148 .It Sy R Ar count No \en
152 bytes of data from the open device.
155 exceeds the size of the data buffer (10 kilobytes), it is
156 truncated to the data buffer size.
159 utility then performs the requested
163 .Sy A Ar count-read No \en
166 successful; otherwise an error in the
167 standard format is returned.
169 was successful, the data read is then sent.
171 .It Xo Sy I Ar operation
172 .No \en Ar count No \en
178 command using the specified parameters.
179 The parameters are interpreted as the
181 representations of the decimal values
186 fields of the structure used in the
189 The return value is the
191 parameter when the operation is successful.
193 Return the status of the open device, as
198 If the operation was successful,
199 an ``ack'' is sent with the size of the
200 status buffer, then the status buffer is
204 Any other command causes
208 All responses are of the form described above.
220 People should be discouraged from using this for a remote
221 file access protocol.