User manual

Configuration file server.cfg
iXOS-JUKEMAN 2.2 User Manual Pre.12/97242
File Meaning
stupid
Allows read and write access to the disc blocks. Used and un-
used block will not be distinguished.
clever
The raw file system will perform a more distinct error handling
for clever files.
It tries to read each block separately. Upon read failure, it
asks the volume’s underlying file system for unused blocks. If
all unreadable blocks turn out to be unused, the raw file sy-
stem succeeds and delivers zero bytes. In case of write failure
on a clever file, the raw file system pretends success if all un-
writable blocks are either unused or do already contain ex-
actly the data that the user tried to write.
This is useful for backups of iXOS-JUKEMAN’s WORM file
system, since it makes the write calls idempotent, and simpli-
fies recovery after a crash during update of a backup through
the raw file system.
The raw file system can be used, for example, to easily make ISO images
on hard disk or to copy disks.
7.2.2 Devices
This section of server.cfg specifies, whether devices will be attached
automatically at server start (setting automatic) or manually (setting
manual). Devices that are not listed will not be attached. It is not re-
quired, to list all devices in this section, as they can always be attached
manually with “cdadm attach <device>” (page 215). Each entry <xyz>
presupposes a corresponding file <xyz>.dev in the JUKEMAN directory.
The GUI on Windows NT expects all devices to be listed in this section.
This is to keep in mind when making changes to server.cfg manually.
Example:
devices {
list { p18 mercury device3 }
p18 { startup { automatic } }
mercury { startup { manual } }
device3 { startup { automatic } }
}
This example defines 3 devices (p18, mercury, device3). The device
names are listed in the list { } section. The following lines specify the