exports_ccase

List of VOBs to be accessed by non-VersionVault hosts

Applicability

Product

Command type

VersionVault

data structure

Platform

UNIX®

Linux®

Synopsis

  • Exports table entry:

    Solaris:

    VOB-tag [ –ro ]

    [ –ro=client [ :client ]... ]

    [ –rw=client [ :client]... ] ]

    [ –anon=uid

    [ –rw ] [ –root=host [ :host]... ]

    All other platforms:

    VOB-tag [ options ] [ netgroup | hostname ] ...
  • Standard options:

    Solaris:

    None.

    All other platforms:

    ro, rw, anon, root, access

  • Default options:

    Solaris:

    –rw

    All other platforms:

    rw, anon=nobody

Description

A host that has not installed VersionVault can still access any VOB, using NFS. For the procedure to set up non-VersionVault access to a VOB, see the Help.

Examples

  • A VersionVault host, saturn, wants to export a VOB mounted at /vobs_proj, as seen through view beta. This line exports the VOB to all hosts in the network:

    /view/beta/vobs_proj

    A non-VersionVault host soft-mounts the VOB with this file system table entry:

    saturn:/view/beta/vobs_proj /
    vvault_vobs_proj nfs rw,noauto,soft,timeo=300,retrans=10   0   0

    Another host hard-mounts the VOB with this file system table entry:

    saturn:/view/beta/vobs_proj /vobs_proj nfs rw,hard 0   0

  • Export a VOB to netgroup pcgroup, and also to individual host newton.

    /view/beta/vobs_proj –w=pcgroup:newton

    Solaris

    /view/beta/vobs_proj –access=pcgroup:newton

    All other architectures

Notes

The VersionVault installation procedure creates a template /etc/exports.mvfs, all of whose lines are commented out.

Files

Solaris

/etc/exports.mvfs /etc/init.d/versionvault