heh. :)

sounds like the same dance i had to do a couple of months ago.

coda spits out information into its logs before it crashes. look for
errors in the last couple of lines of /usr/coda/etc/console and
possibly /usr/coda/etc/venus.log

you can also run gdb -p [pid] on the zombie venus process. in my venus
installation, it doesn't actually leave a core file hanging around,
but you can run gdb on the same lingering venus process.

please post anything you're able to dig out to the list. i would be
curious to know if you're getting the same type of crashing that i've
been getting.

On 06/23/04, Gabriel Wicke <groups_at_gabrielwicke.de> wrote: 

> Hello,
> 
> thanks to Jan's great help i've got a coda server running now at
> wikipedia.org and at home. The home one holds a few Gb of mp3's
> currently, venus cache is set to 6Gb. 8Gb venus cache crashed rather often
> on a restart with full cache, 6Gb seems to be more reliable. Is this to be
> expected or should i look for something in gdb?
> 
> I've just set up http://coda.wikidev.net, a wiki that's intended to
> simplify coda documentation updates/improvements a bit.
> I've done some benchmarks on small file performance for Coda vs. NFS, will
> post those results in the wiki soon.
> -- 
> Gabriel Wicke
> 
> 

-- 

steve simitzis : /sim' - i - jees/
          pala : saturn5 productions
 www.steve.org : 415.282.9979
  hath the daemon spawn no fire?