Here is a complete transcript: 58 $ vice-setup Welcome to the Coda Server Setup script! You already have a file //etc/server.conf! Continueing will remove that file. Do you want to continue? [yes/no] yes Setting up config files for a coda server. Do you want the file //etc/server.conf created? [yes] What is the root directory for your coda server(s)? [/vice] Setting up /vice. Directories under /vice are set up. Is this the master server, aka the SCM machine? (y/n) y Setting up tokens for authentication. The following token must be identical on all servers. Enter a random token for update authentication : elephant The following token must be identical on all servers. Enter a random token for auth2 authentication : elephant The following token must be identical on all servers. Enter a random token for volutil authentication : elephant tokens done! Setting up the file list for update client Filelist for update ready. /etc/services already has new services registered! Good. /etc/services ready for Coda Now installing files specific to the SCM... Setting up servers file. Enter an id for the SCM server. (hostname beaky) The serverid is a unique number between 0 and 255. You should avoid 0, 127, and 255. serverid: 1 done! 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) : codaroot 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: 2 Enter the username of this user: cadmin An initial administrative user cadmin (id 2) with Coda password changeme now exists. A server needs a small log disk partition, preferrably on a disk by itself. It also needs 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 running. Are you ready to set up RVM? [yes/no] yes What is your log partition? /mnt/scratch/logpartition 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)? /mnt/scratch/datapartition 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. Pick 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: /mnt/scratch/logpartition, size 2M. --- data area: /mnt/scratch/datapartition, 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. done. 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 file data [/vicepa]? Shall I set up a vicetab entry for /vicepa (y/n) y Select the maximum number of files for the server. [256K, 1M, 2M, 16M]: 256K Server directory /vicepa 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 updatesrv as: updatesrv - start updateclnt as: updateclnt -h beaky - start the fileserver: startserver & - wait until the server is up: tail -f /vice/srv/SrvLog - create your root volume: createvol_rep codaroot E0000100 /vicepa - setup a client: venus-setup beaky 20000 - start venus: venus - enjoy Coda. - for more information see http://www.coda.cs.cmu.edu. Sat Sep 06 04:39 PM 4 root@beaky:~ 59 $ auth2 Sat Sep 06 04:40 PM 4 root@beaky:~ 60 $ rpc2portmap Sat Sep 06 04:40 PM 4 root@beaky:~ 61 $ updatesrv Sat Sep 06 04:40 PM 4 root@beaky:~ 62 $ updateclnt -h beaky Creating /vice/spool Sat Sep 06 04:40 PM 4 root@beaky:~ 63 $ startserver & [1] 20565 Sat Sep 06 04:40 PM 4 root@beaky:~ 64 $ grep: /vice/srv.conf: No such file or directory [1]+ Done startserver Reproducible: Always Steps to Reproduce: 1. follow the steps in the transcript above as closely as possible 2. 3. Actual Results: Sat Sep 06 04:40 PM 4 root@beaky:~ 63 $ startserver & [1] 20565 Sat Sep 06 04:40 PM 4 root@beaky:~ 64 $ grep: /vice/srv.conf: No such file or directory [1]+ Done startserver Expected Results: Sat Sep 06 04:40 PM 4 root@beaky:~ 63 $ startserver & [1] 20565 Sat Sep 06 04:40 PM 4 root@beaky:~ 64 $ BTW I had to hack all the vice-setup scripts to prepend /etc to all codaconf commands as per bug 26233 (this was before I discoverd it!). 4 $ emerge info Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.21) ================================================================= System uname: 2.4.21 i686 AMD Athlon(tm) XP 1800+ distcc 2.9 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.2 [enabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /var/bind /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/init.d /etc/xfce /etc/X11/xkb /etc/afs/C /etc/afs/afsws /etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs sandbox ccache userpriv usersandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/mnt/monster/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib directfb gtkhtml gdbm berkdb slang readline tetex aalib nas bonobo svga tcltk java guile mysql postgres X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gtk qt motif opengl mozilla ldap cdr dga doc dvd faad fbcon lirc mbox mozcalendar mozp3p mozsvg mozxmlterm oav odbc plotutils samba sse usb -alsa -arts -gnome -kde"
I'll look over this a bit more. The automated setup of coda is a pain. Thanks for the transcript it will help when I/someone else gets around to automating the setup.
Heh, glad you liked the transcript ;) Just to advise you I am no longer pursuing this approach now, too much reformatting involved to retrofit easily into my network. I was quite impressed by the way it worked though! All the best.
You were referring to bug 26233, which has been closed some time ago. I have not noticed any problems with the new coda ebuilds. Can I close this one?
Well, I've since moved on from the employment for which I was trying coda, so I'm happy to take your word for it ;)
Oki, marking this one fixed. Thanks. =]
