The
NT version of iXOS-JUKEMAN is compatible with many different environments,
including mixed environments. It supports the NFS protocol, making it a true
NFS server. UNIX clients simply mount it as they mount any network file system.
Simultaneously, it presents all disks in a native file system for NT, which can
be exported through all available protocols.
When the host starts, the iXOS-JUKEMAN server is started. Depending on the
set-up of the views, new drive letters appear for the views. If you did not
modify the views configuration, the view views_pc will be mapped to
drive letter X:. All disks of all connected devices will be displayed
as subdirectories of X:. The drive letter Y: is the view
views_rr. These two views are shared for NFS clients automatically. PC
clients can map X: and Y: as network drives provided these
drive letters are shared. The Root view, containing both views_pc and
views_rr, is mapped to drive letter Z:. It is also shared for
NFS clients.
The disks can be accessed using the File Manager on the server. The drive
letters or directories can be shared using the standard operating system
functions (for administrators or super users).
All views you set up in addition to the default views must be explicitly
shared. This can be easily done with the Windows NT Explorer. For example, if
you configured a view which is mapped to drive letter W::
In the Explorer, move the mouse pointer to the drive letter or directory you wish to share and click the right mouse button. Select [SHARING] from the pop-up menu. A dialog will pop up in which the drive letter or directory can be shared for the clients.
The following problems may occur in some cases:
* Sometimes a PC client has to deal with long file names and cannot handle
them. This happen for instance if a Rock Ridge view is mounted -- the PC format
view automatically converts the disk names to 8.3. The solution to this problem
is to rename the disks on the server. This can be done with the Windows NT
Explorer, with a dialog of the administration client (see "Rename disks" on
page 116) or with the command cdadm rename, described on page 234.
* Some CD software assumes the root directory of a disk to be the same as the
root directory of the drive, not taking into account the disk name as part of
the path. As a result an installation may fail, because the appropriate files
cannot be located. If this happens, share the corresponding subdirectory, map
it as a network drive on the client PC and the installation will work.
* To execute programs on the server from the iXOS-JUKEMAN file system the disks
have to be mapped as a network drive on the server. It is not possible to start
programs from the drive letters created with the views set-up.
If
no NFS is active under UNIX iXOS-JUKEMAN will take on all NFS services (NFS
demon, mount demon, and even the portmapper). If NFS is active however,
iXOS-JUKEMAN has to cooperate with the nfsd and especially the
rpc.mountd daemon. This requires your help.
rpc.mountd monitors all file systems, including the iXOS-JUKEMAN file
system. If clients mount a network file system, they request a root file handle
from rpc.mountd. This file handle is the key for all further requests
to the standard nfsd or iXOS-JUKEMAN's NFS-Jukebox-Server. It is not
possible to access the network file system without this key.
A root file handle can only be generated, if there is a root for the file
system. For that reason, you must create an empty directory for each view. The
hierarchy of the directories created reflect the hierarchy of the views. A
subdirectory must be created for each subview. The views are normally
/views_rr for the Rock Ridge format and /views_pc for the PC
format. Any other file names are possible as well (although they do not comply
with the standard server.cfg file and must be entered into this file
accordingly).
If, for example, the views set-up corresponds to the structure shown below, the
following directories must be created on the UNIX server:
mkdir /view_1
mkdir /view_2
mkdir /view_3
mkdir /view_3/view_3a
mkdir /view_3/view_3b
Next you export a file system by telling rpc.mountd to give the file
handles to clients. Most flavors of UNIX maintain a file /etc/exports
(Solaris: see below) containing all exported file systems. You can simply add a
line to this file containing just the character /. This will tell
rpc.mountd to export all views of the server file system. Please note,
that this will also cause all other directories of the server to be shared. It
is recommended to export only the directories representing the views. To do
this, add the following lines to /etc/exports:
/views_pc
/views_rr
This will export the standard views to all hosts. You can also restrict access permissions to certain hosts:
/views_pc -ro
/views_rr donald daisy garfield localhost
These lines will export /views_pc read-only to all hosts and
/views_rr to the hosts donald, daisy,
garfield and the server itself. Please note that the entry
localhost is mandatory if specifying certain hosts.
On Solaris the exported file systems are listed in the file
/etc/dfs/dfstab. To export the standard views, add the following lines
to the file:
share -F nfs /views_pc
share -F nfs /views_rr
On some UNIX systems (Solaris and others), the change does not take effect
immediately. On Solaris, call the commands unshareall and
shareall to update the export list. Other UNIX systems offer the
exportfs command. Use exportfs -a to export all file
systems. Another method is to reboot the server. You can easily test if the
directories are exported by using showmount -e. When you start
iXOS-JUKEMAN, it tests whether the directories for all views are exported by
requesting the file handle from rpc.mountd. It stops if it cannot get
a file handle, and prints a message in the log file.