(Illustration by Gaich Muramatsu)
"Sergio Romano" <sergio_at_arroba.com.ar> wrote: > > Any guide to it? What must we look for? > > Must the coda servers (codasrv, auth2, update) be running or just the coda.o > module installed and thats it? They are all different things, and should all be there for a working system: codasrv: The Coda file server, must be running on server(s). It was used to be named "srv". auth2: The authentication server, must be running on an authentication server(s) (could be the same machine(s) as any server(s)). update: Actually, I think you mean updateclnt and updatesrv (and don't confuse with the "update" program use by the Linux OS). They are the programs use to make sure non-SCM server get the same database files (such as VSGDB, VLDB etc) as the SCM server. In other words, when you make change to those database files on a SCM, sooner or later they will be get propagated to all other non-SCM server. "updateclnt" should always run on non-SCM server, and "updatesrv" should always run on SCM machine. Umm..., it used to be the case that there is another program called "updatemon" which monitors and makes sure that updateclnt and updatesrv are always up and running. Has it been retired ? I couldn't find it in recent Coda release (mines is 4.6.1). coda.o: The kernel module that must be up and running in any Coda client. However, usually, you don't need to start it explicitly, it will automatically loaded when you start venus. On my system, I can check if all those babies are there by: *** (On my SCM machine) [root_at_xylophone db]# ps auxww | grep -i codasrv root 434 0.0 0.1 3068 32 ? S Sep 9 0:00 codasrv -trunc 5 -debarrenize -nosalvageonshutdown -nodumpvm -rvm /dev/hdb1 /dev/hda5 39690240 root 1240 0.0 1.1 844 348 p1 S 11:13 0:00 grep -i codasrv [root_at_xylophone db]# ps auxww | grep -i update root 360 0.0 0.7 1468 232 ? S Sep 9 2:32 updateclnt -h xylophone -q coda_udpsrv root 361 0.0 1.1 1496 356 ? S Sep 9 4:07 updatesrv -p /vice/db root 377 0.0 0.0 728 24 ? S Sep 9 0:00 update (bdflush) (Note that the "update (bdflush)" process is *not* a coda process) [root_at_xylophone db]# ps auxww | grep -i auth2 root 362 0.0 1.7 1588 540 ? S Sep 9 0:00 auth2 *** (On my non-SCM machine) [clement_at_violin clement]$ ps auxww | grep -i codasrv root 357 0.0 60.7 44132 18748 ? S < Sep 10 0:06 codasrv -trunc 5 -debarrenize -nosalvageonshutdown -nodumpvm -rvm /dev/hdc1 /dev/hda8 39690240 [clement_at_violin clement]$ ps auxww | grep -i update root 346 0.0 1.2 1608 376 ? S Sep 10 2:13 updateclnt -h xylophone -q coda_udpsrv root 347 0.0 0.7 1492 216 ? S Sep 10 0:00 updatesrv -p /vice/db root 366 0.0 0.0 728 24 ? S Sep 10 0:00 update (bdflush) (Note that the "update (bdflush)" process is *not* a coda process) [clement_at_violin clement]$ ps auxww | grep -i auth2 clement 700 0.0 1.1 844 344 p0 S 11:17 0:00 grep -i auth2 root 341 0.0 0.9 1588 292 ? S Sep 10 0:00 auth2 -chk *** (On my client) [root_at_duet /root]# lsmod Module Pages Used by coda 12 2 (autoclean) nfs 12 6 (autoclean) 3c59x 3 1 (autoclean) Hope this help. -- Clement ====================================================================== Yui-wah LEE (Clement) Tel: (852)-26098412 Department of Computer Science and Engineering, Fax: (852)-26035024 The Chinese University of Hong Kong Email: clement_at_cse.cuhk.edu.hk ======================================================================Received on 1998-09-11 23:27:52