9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Real basics: authentication
Date: Fri, 10 Jan 2003 12:43:50 -0500	[thread overview]
Message-ID: <c45a7588ec4383686591f425bb78adc7@plan9.bell-labs.com> (raw)
In-Reply-To: <20030110093904.N12514@cackle.proxima.alt.za>

Once you connect to the cpu server, cat /dev/user.
If it says lucio, then you're lucio.  It sounds to me
like the cpu server can't find the auth server.
The cpu server and file server can still chat because
they have the same uid and thus don't need an auth
server.  But when you try to authenticate to the file
server no auth server is found so it connects as none.

On the cpu server, if you run

	g% ndb/csquery
	> tcp!$auth!telnet

does it give you a response?



      reply	other threads:[~2003-01-10 17:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 12:22 Lucio De Re
2003-01-09 14:41 ` Russ Cox
2003-01-10  5:15   ` Lucio De Re
2003-01-10  5:58   ` Lucio De Re
2003-01-10  7:39     ` Lucio De Re
2003-01-10 17:43       ` Russ Cox [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=c45a7588ec4383686591f425bb78adc7@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.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).