>
> It would help if you supply more details, like
>
> what kind of system do you have, OS, version, distribution
> what you installed (client only or server(s) as well)
> how you installed (distribution-specific packages, compiled yourself,
> other)
> what exactly you did when you ran clog
> what happened
> what you expected to happen
>
> Regards,
> Rune
>
>

Hello
The following is my session from starting coda and venus to running clog.
I have installed both client or server, I compiled it myself on Gentoo
Linux.

[EMAIL PROTECTED] ~ $ sudo auth2
[EMAIL PROTECTED] ~ $ sudo updatesrv
[EMAIL PROTECTED] ~ $ sudo updateclnt -h codaroot.example.com
[EMAIL PROTECTED] ~ $ sudo startserver &
[1] 30359
[EMAIL PROTECTED] ~ $ sudo venus &
[2] 30406
[1]   Done                    sudo startserver
[EMAIL PROTECTED] ~ $
Date: Mon 07/30/2007

16:46:48 Coda Venus, version 6.1.2
16:46:48 /usr/coda/LOG size is 3038208 bytes
16:46:48 /usr/coda/DATA size is 12144624 bytes
16:46:48 Loading RVM data
16:46:48 Last init was Sun Jul 29 21:02:17 2007
16:46:48 Last shutdown was dirty
16:46:48 Starting RealmDB scan
16:46:48        Found 3 realms
16:46:48 starting VDB scan
16:46:48        3 volume replicas
16:46:48        1 replicated volumes
16:46:48        0 CML entries allocated
16:46:48        0 CML entries on free-list
16:46:48 starting FSDB scan (4166, 100000) (25, 75, 4)
16:46:48        3 cache files in table (0 blocks)
16:46:48        4163 cache files on free-list
16:46:48 starting HDB scan
16:46:48        0 hdb entries in table
16:46:48        0 hdb entries on free-list
16:46:48 Kernel version ioctl failed.
16:46:48 Mounting root volume...
16:46:48 Venus starting...
16:46:48 /coda now mounted.

[2]+  Done                    sudo venus
[EMAIL PROTECTED] ~ $ ls /coda
codaroot.example.com
[EMAIL PROTECTED] ~ $ ls /coda/codaroot.example.com
[EMAIL PROTECTED] ~ $ clog kdambiec
username: [EMAIL PROTECTED]
Password:
[EMAIL PROTECTED] ~ $ ctokens
Tokens held by the Cache Manager for kdambiec:
    @codaroot.example.com
        Not Authenticated



Reply via email to