-
-.sp
-would use the following devices:
-.sp
-\fI/dev/rmt/tps0d4n\fR\fI/dev/rmt/tps0d5n\fR\fI/dev/rmt/tps0d6n\fR
-.TP
-\fBfile\fR
-This driver emulates a tape device with a set of files in a directory. The
-\fBdriver-info\fR
-field must be the name of an existing directory. The driver will test for a subdirectory of that named
-\fBdata\fR
-and return
-\fBoffline\fR
-until it is present. When present, the driver uses two files in the
-\fBdata\fR
-subdirectory for each tape file. One contains the actual data. The other contains record length information.
-.sp
-The driver uses a file named
-\fBstatus\fR
-in the
-\fBfile\fR
-device directory to hold driver status information, such as tape position. If not present, the driver will create it as though the device is rewound.
-.sp
-The
-\fBlength\fR
-value from the associated
-\fBtapetype\fR
-is used to limit the amount of data written. When the limit is reached, the driver will simulate end of tape.
-.sp
-One way to use this driver with a real device such as a CD-writer is to create a directory for the
-\fBfile\fR
-device and one or more other directories for the actual data. Create a symlink named
-\fBdata\fR
-in the
-\fBfile\fR
-directory to one of the data directories. Set the
-\fBtapetype\fR
-length to whatever the medium will hold.
-.sp
-When
-\fBAmanda\fR
-fills the
-\fBfile\fR
-device, remove the symlink and (optionally) create a new symlink to another data area. Use a CD writer software package to burn the image from the first data area.
-.sp
-To read the CD, mount it and create the
-\fBdata\fR
-symlink in the
-\fBfile\fR
-device directory.
-.SH "AUTHORIZATION"
-.PP
-\fBAmanda\fR
-processes on the tape server host run as the
-\fBdumpuser\fR
-user listed in
-\fBamanda.conf\fR. When they connect to a backup client, they do so with an
-\fBAmanda\fR-specific protocol. They do not, for instance, use
-\fBrsh\fR
-or
-\fBssh\fR
-directly.
-.PP
-On the client side, the
-\fBamandad\fR
-daemon validates the connection using one of several methods, depending on how it was compiled and on options it is passed:
-.TP
-.rhosts
-Even though
-\fBAmanda\fR
-does not use
-\fBrsh\fR, it can use
-.rhosts-style authentication and a
-.rhosts
-file.
-.TP
-.amandahosts
-This is essentially the same as
-.rhosts
-authentication except a different file, with almost the same format, is used. This is the default mechanism built into
-\fBAmanda\fR.
-.sp
-The format of the
-\fI.amandahosts\fR
-file is:
-.sp
-\fBhostname\fR
-[
-\fBusername\fR
-]
-.sp
-If
-\fBusername\fR
-is ommitted, it defaults to the user running
-\fBamandad\fR, i.e. the user listed in the
-\fBinetd\fR
-or
-\fBxinetd\fR
-configuration file.
-.TP
-Kerberos
-\fBAmanda\fR
-may use the Kerberos authentication system. Further information is in the
-\fBdocs/KERBEROS\fRfile that comes with an
-\fBAmanda\fR
-distribution.
-.sp
-For Samba access,
-\fBAmanda\fR
-needs a file on the Samba server (which may or may not also be the tape server) named
-\fI/etc/amandapass\fR
-with share names, (clear text) passwords and (optional) domain names, in that order, one per line, whitespace separated. By default, the user used to connect to the PC is the same for all PC's and is compiled into
-\fBAmanda\fR. It may be changed on a host by host basis by listing it first in the password field followed by a percent sign and then the password. For instance:
-.nf
-
- //some-pc/home normalpw
- //another-pc/disk otheruser%otherpw.fi
-With clear text passwords, this file should obviously be tightly protected. It only needs to be readable by the
-\fBAmanda\fR-user on the Samba server.
-.sp
-You can find further information in the
-\fBdocs/SAMBA\fRfile that comes with an
-\fBAmanda\fR
-distribution.
-.SH "HOST & DISK EXPRESSION"