Problems that I'm having...

[G. David Butler gdb@dbSystems.com]

Kenji Okamoto <okamoto@earth.cias.osakafu-u.ac.jp> writes:
>David Butler <gdb@dbsystems.com> writes:
>> I start the terminal and login as me (gdb) with a password.  There is a
>> sucessful entry in /sys/log/auth.  In the 81/2 window I type cpu and get:
>> 
>> cpu: can't authenticate: auth: AS protocol botch

>In my case, I got

>cpu: can't authenticate: rhyolite(aka your auth): can't connect to AS

>(my situation is different from you, though).

>I know this comes from fail in the authlibrary (authdial()), however,
>I don't know why.....  I need more exersize on Plan 9.   ^_^

I think I had that problem before I entered the authid and password
with auth/changeuser.  Just because you can boot the auth server does
*not* mean that the authid password has been set in /adm/keys.  Chech
that you have a /mnt/keys/authid entry on the auth server.  (Where
authid is the id you input on your file and auth servers, e.g. bootes.)
You have to look on the auth server itself to determine this.  (I love
local namespaces!)

>Kenji

As for my problem, I solved it... in /lib/ndb/local I had:

	il=ticket  port=556

It should be:

	il=ticket  port=566

Sometimes I think that touch typing has its problems.  cpu now works
correctly.  That "protocol botch" message is *real* helpful though!? :-)