From: Will <collumww@yahoo.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Trouble connecting to and/or bringing up auth server
Date: Fri, 17 Jan 2003 14:41:04 +0000 [thread overview]
Message-ID: <66615df7.0301170614.751b6e2c@posting.google.com> (raw)
In-Reply-To: <81180214a9bf468706d859833707ee09@plan9.escet.urjc.es>
> Did you update your /lib/ndb to specify the auth entry?
Yes, and I have made a bit of progress, but some things remain
unclear. One thing I had missed was setting authdom in /lib/ndb/local
on each machine. The current situation is:
Reboot the cpu/auth server.
Reboot the terminal. During the reboot, when prompted for a user name,
any will do; it just trips up on not having directories, etc. if you
give it user that hasn't had the disk/kfscmd 'newuser ...' run on it.
It doesn't seem in touch with the auth server. Does that sound right?
Should it be?
Once the terminal is up, auth/login and telnet (to the cpu machine)
will fail giving a message that seems to indicate that it doesn't know
the auth domain and is doesn't have a key (I don't have the text
(sorry) at the moment, and I've got to actullay get to work here).
Should, in fact, auth/login and telnet work at this point?
Next, trying the cpu command at this point will elicit a little
message about adding a key or something and fail with the message I
wrote in my first posting.
Then, lo and behold, if I try auth/login or telnet they work!
And after a successful auth/login, the cpu command works! So, does one
have to auth/login before cpu will work in all cases?
I don't quite get the relationship between the commands and need to do
some more reading.
Thanks,
Will Collum
prev parent reply other threads:[~2003-01-17 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 9:47 Will
2003-01-16 10:35 ` Fco.J.Ballesteros
2003-01-17 14:41 ` Will [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=66615df7.0301170614.751b6e2c@posting.google.com \
--to=collumww@yahoo.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).