tye /vicepa ftree depth=5,width=8
tye /vicepb ftree width=8,depth=5
taverner /vicepa ftree width=8,depth=5
taverner /usr/vicepb ftree depth=4,width=8
tallis /vicepa ftree width=8,depth=5
tallis /vicepb ftree width=8,depth=5
dvorak /backup1 backup
dvorak /backup2 backup
dvorak /backup3 backup
Where column 1 specifies the server as returned by the system
Column 2 specifies the directory of the Coda data tree which
must be a local file system partition for optimal performance.
NOTE: if a server serves than more than one Coda data
parition, each data partition must have a seperate entry in
Column 3 specifies the Coda partition type.
Column 4 specifies the width and depth of the ftree.
ftree an "inode number" directory and
file naming system for storing the Coda filesystem into a local
file system tree structure: e.g. inode 4711 in base 10 with
width 1 and depth 5 would become 0/4/7/1/1. So, using the above
example, a width of 4 and a depth of 2 would make the file name
4/711. If this storage type is specified, the width and depth
must also be given in the 4th column seperated by a comma.
In the case of the backup coordinator, only the first three
columns are used, with a partition type of backup
specified in the third column.
width the maximum "width" of an ftree
depth the maximum "depth" of an ftree
This file should only be edited on the designated SCM machine
and then allowed to propagate.