From: Christian Kellermann <Christian.Kellermann@nefkom.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] keyfs warnings
Date: Tue, 1 May 2007 17:17:17 +0200 [thread overview]
Message-ID: <20070501151717.GL2624@hermes.my.domain> (raw)
In-Reply-To: <bf908c8c562167f0acedb663f4141b23@coraid.com>
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
* erik quanstrom <quanstro@coraid.com> [070501 15:21]:
> > - truncating the /adm/keys file with echo '' > /adm/keys
> > - rebooting, filling in password and secstore phrase
> > - killing keyfs
> > - starting auth/keyfs on the server console
>
> i don't understand this step. if keyfs is running on the console
> of your auth server, restarting it shouldn't make any difference.
>
> (you should always be dealing with keyfs and changeuser from the
> console of the auth server.)
>
The reason for this is that otherwise I don't see anything on
/mnt/keys, i.e. lc /mnt/keys shows nothing, even after a
auth/changeuser.
> where are you "logging in" from. i assume, since you mentioned this
> is a combined fs/cpu/auth server, that you are drawterming in from
> another machine?
Yes I am using drawterm
>
> >
> > When I now kill/restart keyfs on the server keyfs prints the
> > following warnings:
> > % auth/keyfs
> > keyfs: warning: bad status in key file
> > keyfs: warning: bad status in key file
> > keyfs: warning: bad status in key file
> > 4 keys read
> >
> > 1. Shouldn't there be only 2 keys as I have added 2 users?
> > 2. When trying to auth/debug the user login still fails
> > 3. lc /mnt/keys displays garbage
>
> what is in /mnt/keys on the console after you have just booted the machine?
As I said above it is emtpy.
Thanks,
Christian
--
You may use my gpg key for replies:
pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2007-05-01 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 12:56 Christian Kellermann
2007-05-01 13:13 ` erik quanstrom
2007-05-01 15:17 ` Christian Kellermann [this message]
2007-05-01 15:19 ` C H Forsyth
2007-05-01 15:39 ` Christian Kellermann
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=20070501151717.GL2624@hermes.my.domain \
--to=christian.kellermann@nefkom.net \
--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).