Home
Reference
Review reference information for the product.
HCL VersionVault command reference
HCL VersionVault and HCL VersionVault MultiSite provide a command-line interface that enables access to all product functions. The command line processor supports interactive use, and can also be driven by various scripting languages.
Administrator Commands (base VersionVault and UCM)
These commands are used by VersionVault administrators or any user who performs administrative tasks.
MVFS reporting
These commands report on the HCL VersionVault Multiversion File System.
mount_ccase
Mount and unmount commands for VOBs and the viewroot directory

Reference
Review reference information for the product.
- HCL VersionVault command reference
  HCL VersionVault and HCL VersionVault MultiSite provide a command-line interface that enables access to all product functions. The command line processor supports interactive use, and can also be driven by various scripting languages.
  - Commands for developing software
    These commands are used by software developers and others who work with resources that are under HCL VersionVault control. Most of the cleartool commands used by developers who use the VersionVault local client are also available as rcleartool commands for users of the VersionVault remote client.
  - Commands for building software (base VersionVault and UCM)
    These commands are useful for building software, especially in a dynamic view.
  - Administrator Commands (base VersionVault and UCM)
    These commands are used by VersionVault administrators or any user who performs administrative tasks.
    - Importing assets from other configuration management systems
      VersionVault provides a number of utilities that enable you to import files, folders, and metadata from other configuration management systems.
    - Managing VOBs and views
      These commands are useful for creating and administering VOBs and views.
    - Managing the HCL VersionVault registry
      The HCL VersionVault registry provides a central repository of information about VOB and view locations and also specifies default values for typical client host settings.
    - MVFS reporting
      These commands report on the HCL VersionVault Multiversion File System.
      - export_mvfs
        Exports and unexports VOBs to NFS clients (non-VersionVault access)
      - exports_ccase
        List of VOBs to be accessed by non-VersionVault hosts
      - mount
        Activates a VOB at its VOB tag directory
      - mount_ccase
        Mount and unmount commands for VOBs and the viewroot directory
      - mvfsstorage
        Lists data container path name for MVFS file
      - mvfsversion
        Displays MVFS version string
      - setcache
        Changes cache settings
      - umount
        Deactivates a VOB
    - Miscellaneous administrator commands and information
      These commands provide administrative interfaces for tasks such as license management, deployment management, and job scheduling.
  - Commands for managing software development projects (base VersionVault and UCM)
    These commands are used by VersionVault project managers, who establish the development policies for software projects.
  - Alphabetical list of all commands
    All commands, listed alphabetically.
- HCL VersionVault MultiSite command reference
  All commands for HCL VersionVault MultiSite, listed alphabetically.

mount_ccase

Mount and unmount commands for VOBs and the viewroot directory

Applicability


Product	Command type
VersionVault	command


Platform
UNIX®
Linux®

Synopsis

The mount_mvfs program must never be invoked explicitly. Instead, use cleartool mount, which invokes the correct architecture-specific mount command.

Description

This reference page describes the mechanisms that mount VOBs as file systems of type MVFS (the VersionVault multiversion file system).

Automatic VOB activation at system startup

At system startup, the architecture-specific VersionVault startup script (see the init_ccase reference page) issues a mount –all command. This activates on the local host all the VOBs that are registered as public in the local host's network region of the VersionVault VOB registry. During this procedure, the architecture-specific mount command performs the actual work of mounting the VOB as a file system of type MVFS. (The command is actually a symbolic link to versionvault-home-dir/etc/mount_mvfs.)

VOB activation after system startup

After system startup, a mount command can be used to activate or reactivate any VOB that is listed in the tags registry.

root can activate any VOB in this way.
Another identity can activate any public VOB, or any private VOB owned by that identity.

Automatic VOB deactivation at system shutdown

At system shutdown, the architecture-specific VersionVault startup script is invoked with the stop option to execute the VersionVault shutdown procedure. As part of this procedure, a umount –all command deactivates all VOBs currently active on the local host. On all platforms, umount –all invokes the standard umount(1M) utility directly.

Individual VOB deactivation

While VersionVault is running, a umount command can be used to deactivate any mounted VOB:

root can deactivate any VOB in this way.
A non-root user can deactivate any public VOB, or any private VOB owned by that user.

See also

exports_ccase, init_ccase, mount, umount, mount(1M), umount(1M), mountall(1M) (some architectures)

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.