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. All advertising materials mentioning features or use of this software
13
.\" must display the following acknowledgement:
14
.\" This product includes software developed by the University of
15
.\" California, Berkeley and its contributors.
16
.\" 4. Neither the name of the University nor the names of its contributors
17
.\" may be used to endorse or promote products derived from this software
18
.\" without specific prior written permission.
20
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32
.\" $Id: rmt.8.in,v 1.7 2002/01/16 09:32:14 stelian Exp $
39
.Nd remote magtape protocol module
44
is a program used by the remote dump and restore programs
45
in manipulating a magnetic tape drive through an interprocess
46
communication connection.
48
is normally started up with an
56
program accepts requests specific to the manipulation of
57
magnetic tapes, performs the commands, then responds with
58
a status indication. All responses are in
62
Successful commands have responses of:
63
.Bd -filled -offset indent
65
.Sy A Ar number No \en
72
representation of a decimal number.
73
Unsuccessful commands are responded to with:
74
.Bd -filled -offset indent
76
.Xo Sy E Ar error-number
77
.No \en Ar error-message
84
is one of the possible error
89
is the corresponding error string as printed
92
The protocol is comprised of the
93
following commands, which are sent as indicated - no spaces are supplied
94
between the command and its arguments, or between its arguments, and
96
indicates that a newline should be supplied:
99
.It Xo Sy \&O Ar device
100
.No \en Ar mode No \en
107
is a full pathname and
111
representation of a decimal
112
number suitable for passing to
114
If a device had already been opened, it is
115
closed before a new open is performed.
116
.It Xo Sy C Ar device No \en
118
Close the currently open device. The
120
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.
139
bytes from the connection, aborting if
140
a premature end-of-file is encountered.
141
The response value is that returned from
146
.It Sy R Ar count No \en
150
bytes of data from the open device.
153
exceeds the size of the data buffer (10 kilobytes), it is
154
truncated to the data buffer size.
156
then performs the requested
160
.Sy A Ar count-read No \en
163
successful; otherwise an error in the
164
standard format is returned. If the read
165
was successful, the data read is then sent.
167
.It Xo Sy I Ar operation
168
.No \en Ar count No \en
174
command using the specified parameters.
175
The parameters are interpreted as the
177
representations of the decimal values
182
fields of the structure used in the
184
call. The return value is the
186
parameter when the operation is successful.
189
Return the status of the open device, as
193
call. If the operation was successful,
194
an ``ack'' is sent with the size of the
195
status buffer, then the status buffer is
200
Any other command causes
204
All responses are of the form described above.
212
People should be discouraged from using this for a remote
213
file access protocol.
217
backup suit was ported to Linux's Second Extended File System
218
by Remy Card <card@Linux.EU.Org>. He maintained the initial versions
219
of dump (up and including 0.4b4, released in january 1997).
221
Starting with 0.4b5, the new maintainer is Stelian Pop
223
<stelian@popies.net>.
227
backup suit is available from
229
http://dump.sourceforge.net
added
removed
rmt/rmt.8.in
