From: john@csplan9.rit.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] auth/changeuser problems
Date: Sun, 25 Feb 2007 20:48:23 -0500 [thread overview]
Message-ID: <18eef0741ddb2412a1ac2e76c14d6d2e@csplan9.rit.edu> (raw)
In-Reply-To: <aa8a6b8ba16f87f99b0210d744dcc1da@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
I'm sending this from my machine. The output of ndb/ipquery sys csplan9 auth is
auth=csplan9.rit.edu
Running auth/debug gives me the following:
p9sk1 key: proto=p9sk1 user=bootes dom=rit.edu !hex? !password?
successfully dialed auth server
password for bootes@rit.edu [hit enter to skip test]:
ticket request using bootes@rit.edu key succeeded
cpu server owner for domain rit.edu [bootes]:
password for bootes@rit.edu [hit enter to skip test]:
ticket request using bootes@rit.edu key succeeded
John
[-- Attachment #2: Type: message/rfc822, Size: 3109 bytes --]
From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] auth/changeuser problems
Date: Mon, 26 Feb 2007 01:02:11 +0000
Message-ID: <aa8a6b8ba16f87f99b0210d744dcc1da@quintile.net>
To change your password just run passwd, auth/changeuser is an adminstrative
command to change somone elses password rather than your own. It is normally
run from the auth server's console.
The error "cs: cannot translate service" is more telling, I think your
lib/ndb/local doesn't have enough info, to tell ndb/cs how to find your
auth server.
You can check by typing:
ndb/ipquery sys $sysname auth
If you run auth/debug you can check this and some other bits and pieces.
-Steve
prev parent reply other threads:[~2007-02-26 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 21:11 John Floren
2007-02-25 22:12 ` erik quanstrom
2007-02-25 22:25 ` John Floren
2007-02-25 22:31 ` erik quanstrom
2007-02-26 22:05 ` john
2007-02-26 1:02 ` Steve Simon
2007-02-26 1:48 ` john [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=18eef0741ddb2412a1ac2e76c14d6d2e@csplan9.rit.edu \
--to=john@csplan9.rit.edu \
--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).