An export view for non-ClearCase® access
exports a view-extended pathname to the VOB mount point.
Procedure
-
A
DevOps Code ClearCase client host that is configured to
use the MVFS activates (mounts) the VOB.
The VOB must have been marked for export by using the –ncaexported option to
mkvob or mktag.
- The host starts an export view, through which the VOB is
accessed by non-ClearCase hosts.
An export view must meet two requirements:
- It must be marked for export by using the –ncaexported option
to mkview or mktag.
- If the view has tags in multiple registry regions, the exported
tag must be in the view server host's region.
- The host uses an /etc/exports.mvfs file
to export a view-extended pathname to the VOB mount point—for example, /view/exp_vu/vobs/proj.
Note: Any symbolic link in this VOB mount point must be a relative
symbolic link. Any absolute target of a symbolic link that includes
the VOB mount point must be changed to relative for the export to
work.
- One or more non-ClearCase hosts
in the network perform an NFS mount of the exported pathname.
Example
See the
exports_ccase reference page
for the procedure specific to your operating system. It describes
the simplest (and recommended) setup, in which the VOB and the export
view are located on the same host. The following sections discuss
this issue in greater detail, including advice on how to proceed if
you do not want to locate the export view on the VOB server host.
Note: If you modify an export view's config spec, verify that
all users who might currently have mounted the view for non-ClearCase access
unmount and then remount the view. Remounting the view ensures access
to the correct set of files as specified in the updated config spec.