Hi I installed it successfully yesterday.

That's what I did:

I ran the server, auth2 server and all stuff in coda-update init script
(i.e. rpc2portmap, client and server update daemons)
I also checked out the log messages from those programs.

Than at SCM I added the new user via pdbtool.
If I did not do this, but used au nu at client I could not
get login work (dunno why ? :)

When playing with new accounts it is important to choose
some high uid (i.e. 600) not 1,2 etc...

after exit from pdbtool I restarted the coda-update
stuff. Than at client I used au nu, which sets the
password to the user added via pdbtool.

Then just created new volume, ran clog and mount it
as coda admin.

This is the process that works for me.

Hope this helps.

Now I got 1 question for Coda ppl.
I could not restrict access to any user that
belongs to System:AnyUser. For example:
I have /coda/server_name/dir
dir has rl for System:AnyUser.
user1 has -r but still can read anything in dir
Is there any way to force the rights?

Thanks

Jan

On Tue, 14 Sep 2004, redirecting decoy wrote:

> Hello,
>
> I am new to coda, only been toying with it for 2 days.
>
> I am using version 6.0.6 on a linux machine.  I am
> having problems with coda authentification using a new
> coda install.
>
> I have 2 machines, Machine1 is the server, Machine2 is
> the client.  I followed the documentation in setting
> up the server, and can see the /coda volume(s) on
> Machine1.  I can also see the volume on machine2.
> However I only have read-only access to the fs.  From
> Machine21 as the user "coda", which is the user I used
> during the server install, I try to do the following:
> "clog -host pa-wb-001.public" (machine1).  This gives
> me the following error.
> "Invalid login: (RPC2_NOBINDING (F))"
>
> /vice/auth2/AuthLog <--- is empty, and there is no
> relevent information in my other logfiles.  auth2 is
> running.    I get the same error from Machine2, anyone
> have any ideas why this is so ?
>
> Open to any suggestions.  Thanks.
>
> -RD
>