No I didn't have a token .. Thank you for the information
(I didn't realise it was necessary on the server itself.. shame on me)

How can I get a never ending token. I can only see cron but I am looking for
a better solution.
This server is going to serve mail ans store it in the coda directory to
insure redunduncy.

The master and server must always be able to write on the coda fs.
The two server are interconnected connected with dedicated ethernet cards.

Can I block the venus port on my "public interface" to avoid any remove
mount ?


----- Original Message -----
From: "LEE, Yui-wah (Clement)" <clement_at_pc89117.cse.cuhk.edu.hk>
To: <codalist_at_telemann.coda.cs.cmu.edu>
Sent: Saturday, March 25, 2000 7:53 AM
Subject: Re: Coda directory read-only


>
>
> On Fri, 24 Mar 2000, Thomas Mangin Office wrote:
>
> > Hello,
> >
> > I set up coda all was fine (after few try) server + client.
> > I then changed the vfstab to point on the computer itself and rebooted
> > I then got a empty coda directory but I can write anything in it ...
> > Any clue of what I mis-done
>
> Have you got the necessary token?  And how is the ACL of the directory
> set?  "ctokens" will show what tokens you have, "clog" will help you
> to obtain a token, "cfs la <dir>" will show what ACL the <dir> has.
>
> E.g.
>
> [clement_at_aria c.clement]$ clog clement
> username: clement
> Password:
> [clement_at_aria c.clement]$ ctokens
>
> Token held by the Cache Manager:
>
> Local uid: 6822
> Coda user id: 6822
> Expiration time: Sun Mar 26 16:51:34 2000
>
> [clement_at_aria c.clement]$ cfs la /coda/usr/c.clement/
> System:Administrators  rlidwka
>              clement  rlidwka
>
> -- Clement
>
>