On Mon, Aug 30, 1999 at 01:22:30PM -0700, Craig Hughes wrote:
> /coda has never been mounted in the first place. But yes, I did try that.
> I've rebooted the machine, rebooted both machines, clean-reinstalled
> everything, etc, etc. No fix.
>
> C
When venus is killed right after printing 'Venus starting', it must be
the child that is the culprit. And as the server is trying to set up
a callback connection, the client is able to talk to the server.
Nothing logged in /usr/coda/etc/console?
Try to start venus as `venus -d 10', maybe a higher debug level will
reveal something here. ps. normally when venus crashed/dies it is put
into an endless loop, as that is the best way to debug rvm related
problems. It also means that venus will keep certain sockets/resources
allocated which will cause a second venus to fail during startup.
If you want to start from a clean slate, a reboot shouldn't be
necessary. I do the following to get a fresh/reinitialized client.
# killall -9 venus
# umount /coda
# rmmod coda
# touch /usr/coda/venus.cache/INIT # or start venus with '-init' flag
# venus
Jan
