A workspace whose workspace tree is network-accessible through a share, can be accessed from any client machine — running UNIX/Linux or Windows. The share can be configured through Samba/SMB or some other network file system. It must make the actual storage location available through a machine name and a simple “share name”: a name that looks like a single pathname component.
The technique in Accessing a Windows Workspace From Multiple Windows Clients on page 13 relies only on Windows operating system facilities. But the “universal workspace access” technique requires the maintaining of a pathname-mapping file for use by the AccuRev Server. If a “share” (that is, shared directory) has an entry in the pathname-mapping file, any workspace located on that share can be used on all AccuRev client machines capable of accessing the machine where the share resides.
The pathname-mapping file is a text file, share_map.txt, which must be located in the AccuRev
site_slice directory on the AccuRev Server machine. It maps share names to absolute pathnames. Each line of
share_map.txt consists of three
TAB-separated fields, describing one share. For example:
This entry says, “a share named accwks is physically located on machine
jupiter, at absolute pathname
/public05/accurev_workspaces”. More generally:
The accurev show wspaces (or the GUI’s
View > Workspaces) command displays the locations of existing workspaces in the repository. The pathnames always use forward slashes, even if they are Windows pathnames.
AccuRev can record the location as an absolute pathname on its machine:
Universal workspace access requires that a workspace’s location be recorded as an absolute pathname in the workspaces table. (Note that the sharing technique described in
Accessing a Windows Workspace From Multiple Windows Clients on page 13 has the opposite requirement: workspace locations must incorporate the share name.) In addition, the “Host” name listed in this table for a workspace must exactly match the first field in some
share_map.txt entry. Beware of domain name discrepancies — for example,
jupiter vs.
jupiter.mycorp.com.
If there’s a discrepancy between a machine’s name in a share_map.txt entry (say,
jupiter) and its name in the workspaces table (say,
jupiter.mycorp.com), change the workspace table entry: