> Does anyone have a solution to the problem of keeping
> /usr/vice/etc/CellServDB up-to-date on all your AFS clients?
>
> Also, how to keep cell mounts consistent with CellServDB?
>
> Are there any Transarcian recommendations about this?
I've included the man page of our local hack. The sources are in
/afs/uni-hohenheim.de/home/schaefer/afsdev/ucsdb-0/
Normal output looks like this:
Invalid cell: pub.nsa.hp.com
New cell: sleeper.nsa.hp.com
New servers in cell: cs.cmu.edu
With special options and the necessary privileges the program will
create/remove mount points of new/vanished cells on its own.
Tobias Schaefer
[EMAIL PROTECTED]
ucsdb(8) (2 February 1995) ucsdb(8)
NAME
ucsdb - update CellServDB of an AFS client machine
SYNOPSIS
ucsdb [-nmu] <local CellServDB> <master CellServDB>
<extension list>
DESCRIPTION
The program takes the central CellServDB (maintained by
Transarc) and possibly an own file of local extensions and
creates a combined list of their entries. If an entry is
both in the local extensions file and in the master file, an
error message is written to stderr. If these entries
contain conflicting information the local extensions file
takes precedence. A conflict is reported in an error message
to stderr.
The program reads the local CellServDB (if it exists) and
compares it to the previously created list. In the case of
changed or new entries a new CellServDB is written and the
changed information is communicated to the cache manager via
"fs newcell" calls.
OPTIONS
-n no action is performed
-m missing cells are mounted into the AFS tree
-u mountpoints of vanished cells are removed from the AFS
tree
FILES
/usr/vice/etc/CellServDB
/usr/vice/etc/ExtensionList
/afs/transarc.com/service/etc/CellServDB.export
AUTHOR
Tobias Schaefer, 1995
BUGS
Will exit, if local CellServDB file does not exist.
Will remove local cell if its entry is neither in master
CellServDB nor in extension list.
Page 1 (printed 3/6/95)
