Coda File System

Cant keep the server alive

From: Žolli <>
Date: Tue, 18 Apr 2000 16:18:02 +0200
[root_at_colio /]# vice-setup
Setting up config files (under /vice).
Directories under /vice are set up.

Setting up tokens for authentication.
The following tokens must be identical on all servers.
Enter a random token for auth2 authentication : thorvald
The following tokens must be identical on all servers.
Enter a random token for volutil authentication : thorvald
tokens done!

Setting up the file list for update
filelist for update ready.

Populating /vice/vol...
lockfiles created.
/etc/services already has new services registered! Good.
/etc/services ready for Coda
Is this the master server, aka the SCM machine? (y/n) y
Now installing files specific to the SCM...

Setting up servers file.
Enter an id for this server.
The serverid should be a number between 0 and 255 *avoid 0, 127, and
serverid: 1
Initializing the VSGDB to contain the SCM as E0000100
/vice/db/VSGDB set up

Setting up ROOTVOLUME file
Enter the name of the rootvolume (< 32 chars) : volumeName

Setting up users and groups for Coda

You need to give me a uid (not 0) and username (not root)
for a Coda System:Administrator member on this server,
(sort of a Coda super user)

Enter the uid of this user: 1234
Enter the username of this user: tholli
An initial administrative user tholli (id 1234)
with Coda password changeme now exists.

You need a small log disk partition, preferrably on a disk by itself.
You need a metadata partition of approx 4% of you filespace.

For trial purposes you may give oridnary files instead of raw
partitions. Keep all size small if you do this.
Production servers will want partitions for speed.

WARNING: you are going to play with your partitions now.
verify all answers you give.
WARNING: these choices are not easy to change once you are up and

Are you ready to set up RVM? [yes/no] y

What is your log partition? /partitions/log

The log size must be smaller than you log partition.
We recommend not more than 30M log size, and 2M is a good choice.
What is your log size? (enter as e.g. '2M') 2M

What is your data partition (or file)? /partitions/data

The data size must be approx 4% of you server file space.
We have templates for servers of approx: 500M, 1G, 2.2G, 3.3G, 8G
(you can store less, but not more on such servers).
The corresponding data sizes are  22M, 44M, 90M, 130M, 315M.
(use 315M only on very fast machines)
ick one of the defaults, otherwise I will bail out

What is the size of you data partition (or file)
[22M,44M, 90M, 130M, 200M, 315M]: 22M

WARNING: DATA and LOG partitions are about to be wiped.

  --- log area: /partitions/log, size 2M.
  --- data area: /partitions/data, size 22M.

Proceed, and wipe out old data? [y/n] y

LOG file has been initialized!

Rdsinit will initialize data and log.
This takes a while.
rvm_initialize succeeded.
Going to initialize data file to zero, could take awhile.
rds_zap_heap completed successfully.
rvm_terminate succeeded.
RVM setup is done!

Your server directories will hold the files (not directories).
You can currently only have one directory per disk partition.

Where shall we store your data [/vicepa]? /vicepa
Shall I set up a vicetab entry for approx 256000 files for /vicepa (y/n)
Now initializing the partition. This takes a while....
Partition /vicepa: inodes in use: 0, total: 262144.

Date: Tue 04/18/2000

15:24:34 Partition /vicepa: 1459654K available (minfree=5%), 1265381K

Server directory is set up!

Congratulations: your configuration is ready...and now
to get going do the following:
 - start the auth2 server as: auth2
 - start rpc2portmap as: rpc2portmap
 - start updateclnt as:  updateclnt -h colio -q coda_udpsrv
 - start updatesrv as: updatesrv -p /vice/db
 - start the fileserver: startserver &
 - wait until the server is up: tail -f /vice/srv/SrvLog
 - create your root volume: createvol_rep volumeName E0000100 /vicepa
 - setup a client: venus-setup colio 20000
 - start venus: venus
 - enjoy Coda.

[root_at_colio /]# auth2
[root_at_colio /]# rpc2portmap
[root_at_colio /]# updateclnt -h colio -q coda_udpsrv
[root_at_colio /]# Creating /vice/spool

[root_at_colio /]# updatesrv -p /vice/db
[root_at_colio /]# startserver &
[5] 1728

After this I cant find any SrvLog file so I can even trace the problem

this is in /vice/srv.conf
-rvm /partitions/log /partitions/data 23068672

processes running
root      1230  0.0  1.5  1660  980 ?        S    14:25   0:00 auth2
root      1232  0.0  0.9  1344  576 ?        S    14:25   0:00
root      1234  0.0  1.6  1948 1032 ?        S    14:25   0:00
updateclnt -h colio -q coda_udpsrv
root      1236  0.0  1.7  1980 1076 ?        S    14:26   0:00 updatesrv
-p /vice/db
root      1237  0.0  1.2  1680  796 pts/1    T    14:27   0:00 sh

Cant keep the server alive !!!!!!!!!!!!!!

I used as recomented files both for log and data (created just with

[root_at_colio /]# Creating /vice/spool
The only idea I have is that the creation of the spool directory is not
completed since it is empty after the
vice-setup, but it should probably be since I guess its purpose is just
space for spooling :-)

Since getting the server up and running is quite inportand to me could
somebody please take a quick look?

Received on 2000-04-18 10:23:36