Coda File System

Re: Second SCM setup

From: <>
Date: Thu, 19 Nov 1998 10:26:23 -0500
Khairul Azmi wrote:
> I'm trying to set second coda server(cel_linux1) to my Coda cell. The 
> master coda server (cel_linux2) is functioning well. From the client I 
> can unmount and remount, make changes etc. When setting the second 
> server, I gave the HOSTNAME of the SCM (cel_linux2) but upon starting, 
> the SrvLog gave me this message


The SCM needs to know about the second server, in fact, most if the 
configuration files in /vice/db will be kept in sync between all coda servers
when updateclnt and updatesrv are running. To get a second server running,

1 on the new coda server, install the server that it knows which machine is
  the SCM. (/vice/db/scm should contain SCM's hostname).

2 on the new coda server, start the update daemons.
  (`/etc/rc.d/init.d/update.init start')

3 on the SCM server, add an entry for the new machine in /vice/db/servers
  (every host must have a unique number. This unique number should fall in
   the range of 1 to 255)

4 on the SCM server, add a new volume storage group to /vice/db/VSGDB.
  (f.i. E00000101 cel_linux1 cel_linux2)

5 check if the /vice/db/[servers|VSGDB] files on the second server are now 
  up-to-date with the modifications that were made on the SCM.

If that went fine, it is very likely that the authentication and coda servers
will be able to start correctly on you new machine.

(/etc/rc.d/init.d/auth2.init start ; /etc/rc.d/init.d/codasrv.init start)

Received on 1998-11-19 10:28:12