init_ccase

The startup script resides outside the host's VersionVault installation area. It calls on another script, which resides inside the installation area, to do the actual startup processing. If this other script, versionvault-home-dir/etc/versionvault, cannot be accessed, the startup script enters a retry loop. (This can occur when the VersionVault installation area is located on a remote host and that host is currently unavailable.)

In its retry loop, the startup script tries periodically to invoke versionvault-home-dir/etc/versionvault.The retries continue indefinitely; if you want to terminate the loop, remove the flag file /tmp/VersionVault.retrying.

The startup script runs a standard mount command to mount the viewroot directory as a file system of type MVFS. This mount command is architecture specific:

Architecture	Command
Linux	mount_mvfs –o rw,viewroot /dev/mvfs /view
Solaris	mount –F mvfs –o rw,viewroot /view /view

You can change the extending naming symbol by appending a string to the argument that follows the –o option:

• ,xnsuffix=symbol
• ,–o=xnsuffix=symbol

This specifies a character string to be used on the local host as the VersionVault extended naming symbol. By default, the string @@ is used. Be careful; this option affects the local host only; other hosts may use the default extended-naming symbol or another symbol specified with this mount option.

You can specify a directory other than /view as the viewroot. Whatever directory you specify (for example, /ccasevu) must exist at system startup time. Note that you must specify this directory name twice in the mount command.

Mounting the viewroot directory enables use of VersionVault views on the local host. When a view is activated (by startview, setview, or mktag), its view tag is entered into the viewroot directory. For example, activating a view whose view tag is gamma creates the directory entry /view/gamma. See the pathnames_ccase reference page for a discussion of view-extended path names that use such directory entries.

A mounted viewroot directory is not actually an on-disk directory. Rather, it is a data structure maintained in main memory by the MVFS code loaded into the operating system kernel. The viewroot directory's list of view tags is lost whenever VersionVault operation on the local host is stopped (including an operating system shutdown).

The viewroot directory cannot be exported and cannot be mounted by any other host. Each VersionVault host must have its own viewroot directory.