From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] auth/changeuser problems
Date: Sun, 25 Feb 2007 17:31:20 -0500 [thread overview]
Message-ID: <19f7d1f44bf73a8fef060198b5396078@coraid.com> (raw)
In-Reply-To: <7d3530220702251425k14d28b2ci87d63bc8722f6279@mail.gmail.com>
when the maual page says this
DESCRIPTION
These administrative commands run only on the authentication
server.
i think you should read "on the console of the authentication server".
one problem i've sometimes noticed with changeuser is it can duplicate
lines in /auth/keys.who
- erik
> Well, I know for a fact that I have an nvram partition--I can see it
> in /dev/sdC0, and if I 'cat' it there /is/ some data.
>
> As for keyfs not running, ps | grep keyfs gives me this:
> bootes 66 0:00 0:00 100K Pread keyfs
> bootes 235 0:00 0:00 100K Pread keyfs
> The low PID on the first keyfs makes me think it was launched by
> cpurc, which does in fact contain a line to start keyfs. I've also
> restarted the machine remotely using the 'echo reboot /386/9pccpuf >
> /dev/reboot' trick and the problem persists.
>
> The reason I'm trying to run auth/keyfs as a normal user is so I can
> run auth/changeuser to change my password. What's the deal with
> "passwd", anyway? Although that's the obvious choice for changing my
> password, when I try to run it I get the message "passwd: protocol
> botch: cs: can't translate service".
perhaps you don't have an authserver set in /lib/ndb/local?
- erik
next prev parent reply other threads:[~2007-02-25 22:31 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 [this message]
2007-02-26 22:05 ` john
2007-02-26 1:02 ` Steve Simon
2007-02-26 1:48 ` john
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=19f7d1f44bf73a8fef060198b5396078@coraid.com \
--to=quanstro@coraid.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).