VOB mount options

When a VOB tag is created, options such as ro or exportid might be defined. In the default configuration in which the cleartool mount -all command mounts all public VOBs when HCL VersionVault is started, those options are read from the VersionVault registry and applied to the VOB mount. If a user runs the cleartool mount command and specifies mount options on the command line, cleartool uses the command-line options and ignores the options from the VOB tag registry. This same precedence is implemented for VOB automounting, and a mount request that receives no explicit options from the automounter uses the VOB registry options. However, because of differences in each implementation in an OS of the automounter on some Linux systems, the automounter might insert global options that might cause the VOB tag registry options to be ignored.
For best results, if you have defined VOB tag registry options, check the options on an automounted VOB. If tag options are not been passed through as expected, take these steps:
  1. Modify the /etc/autofs.conf file in your system to set the append_options option to no (and uncomment that line in the file, if necessary).
  2. Modify the /etc/auto.mvfs file to uncomment the line that reads the mount options from the VOB registry entry: 
    #
# For RedHat platforms, if you would like to have the automounted
# vob replace any automounter provided options
# with the vob tag mount options, set APPEND_OPTIONS in autofs
# config file to NO and uncomment out the following line.
# if (/Mount options:/) mopts=(mopts "," $3 )