What additional steps are need when installing a non-SCM
Right after installing the non-scm, the steps would be something
Create the entry in the servers file, make sure that the id is
unique, and not any of 0, 127 or 255 (0, the prefix for replicated
volumes, or (unsigned char)-1).
Create an entry in the VSGDB for both the SCM and the non-scm
server. Ofcourse with an unique VSG number (f.i. E0000101 SCM
Possibly create a vicetab entry for the non-scm's /vicepa, etc.
(if you want to use a centralized vicetab), or make sure that
listed in /vice/db/files to avoid updateclnt
from "updating" this file.
Restart the SCM codasrv.
Run the vice-setup script on the non-scm and go through the
Run updateclnt -h `cat /vice/db/scm`
Check whether the files in /vice/db are in sync with those on
Start the non-scm codasrv process.
Try to create a replicated volume.
Technically the only difference between the SCM and non-SCM
servers is that the SCM server is running the updatesrv and
rpc2portmap processes and that all the other servers are using
those to make local copies of the files in /vice/db. So adding
users and creating volumes should be done on the SCM, otherwise
noone will see the new information (and it will be lost as soon as
updateclnt syncs in an updated version of the