I have a coda client installed on the same box as the coda server it accesses.
For some reason, this seems much flakier than the external clients. It
frequently bombs out:

venus.log tail:
    [ H(07) : 0007 : 16:21:35 ] HDBDaemon just woke up
    [ H(07) : 0007 : 16:21:35 ] DataWalk:  Restarting Iterator!!!!  Reset availability status information.
    [ H(07) : 0007 : 16:21:35 ] Tally for uid=0:
    [ H(07) : 0007 : 16:21:35 ] BeginRvmFlush (1, 4244, F)
    [ H(07) : 0007 : 16:21:35 ] EndRvmFlush
    [ H(07) : 0007 : 16:21:35 ] Tally for uid=0:

    [ H(07) : 0008 : 16:21:35 ] HDBDaemon about to sleep on hdbdaemon_sync
    [ W(20) : 0000 : 16:21:47 ] *****  FATAL SIGNAL (11) *****

venus.err tail:
    16:21:47 Fatal Signal (11); pid 4271 becoming a zombie...
    16:21:47 You may use gdb to attach to 4271

If I bounce the client using the /etc/init.d script, it comes back
up successfully, but consistently dies as soon as I hit it with a
    ctokens
The log looks like this
    16:29:22 RPC2_Bind to 129.42.208.182 port 11957 for callback failed RPC2_NOBINDING (F)
    16:29:22 Worker2: Unbinding RPC connection 14464
and I get the same venus zombie-waiting-for-gdb lossage in the venus logs.

Only fix appears to be flushing the venus dir and reinitialising. 

Is there something wrong with local-client/server interaction? Am I
doing something wrong?
    -Olin