Hi Jan,

Ok I changed from log size 30M to 2M and data size from 315M to 90M.

The server is starting properly.

now I am having problems with the client.  I have the kernel compiled with coda built in rather than a module.  again client
is SuSE 6.0 kernel 2.2.7

I get the following error upon starting venus-setup 

wiggles:/import/src/coda-5.2.7 # venus-setup cruel 20000
/etc/services already has new services registered! Good.
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/adfs.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/affs.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/autofs.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/binfmt_aout.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/binfmt_elf.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/binfmt_java.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/coda.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/ext2.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/fat.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/hfs.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/hpfs.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/isofs.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/lockd.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/minix.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/msdos.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nfs.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nfsd.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp437.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp737.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp775.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp850.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp852.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp855.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp857.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp860.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp861.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp862.o
depmod: *** Unresolved symbols in /lib/modules/2.2.7/fs/nls_cp863.o

It continues for alot longer then this.

when I do venus & I get the following:

wiggles:/ # venus &
[1] 30331
wiggles:/ #
Date: Fri 09/10/99

11:31:03 /usr/coda/LOG setup for size 0x8761e
11:31:03 /usr/coda/DATA initialized at size 0x21d878
11:31:03 brain-wiping recoverable store
11:31:04 loading recoverable store
11:31:05 fatal error -- CommInit: getservbyname failed; check /etc/services
11:31:05 Fatal Signal (11); pid 30331 becoming a zombie...
11:31:05 You may use gdb to attach to 30331


> On Fri, Sep 10, 1999 at 10:04:32AM -0400, squeegy_at_squeegy.org wrote:
> 
> > these are my errors:
> > 
> > First on initializing my rvm data partition
> > I get the following error:
> > 
> > Going to initialize data file to zero, could take awhile.
> > done.
> > ?  ERROR: rds_zap_heap RVM_EINTERNAL.
> > Error in rdsinit. Exiting.
> 
> Well, this means that the recoverable virtual memory (RVM) is not
> correctly initialized.
> 
> Remove /vice/srv.conf and run 'vice-setup-rvm', which takes you through
> the steps for setting up rvm again.
> 
> First set up something simple, 2M log is more than sufficient, and 44 or
> 90M data. It looks like it fails to mmap the data segment, maybe the
> large log was mapped in an overlapping region, or there was not enough
> space for the data segment.
> 
> > Next when I attempt to start the codasrv.init
> 
> Can't start the server without first initializing RVM.
> 
> > If I do a ps ax | grep coda, the codasrv is running as well as the
> > updatesrv and updateclnt and auth2 and startsvr and rpc2portmap
> 
> The server is dead, just idling in an endless loop waiting for someone
> to attach a debugger. You can kill it, as there is nothing to debug.
> 
> Jan
> 
> 



___________________

Jt "The Squeegy" Chiodi

http://www.squeegy.org/
squeegy_at_squeegy.org