9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ish Rattan <ishwar@pali.cps.cmich.edu>
To: <9fans@cse.psu.edu>
Subject: [9fans] keys again
Date: Tue,  5 Jun 2001 12:23:47 -0400	[thread overview]
Message-ID: <Pine.LNX.4.30.0106051222580.24166-100000@pali.cps.cmich.edu> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 645 bytes --]

I removed the files /adm/keys and /adm/keys.who
and recreated keys using /auth/changeuser for each user
in /adm/users..

/sys/log/cron still shows
hostname Jun 5 11:56:12: upas: key not found

command auth/keysfs -p
(after killing keyfs process)
starts new keysfs but it complains
keyfs: warning: bad status in key file
(903 times.., there are not that many users??)

also entries in /mnt/keys are of the form and there are 1031
entries?
---
\x14#n4@}€\x17w€€T€€\x1dA
*€€€€€€€€\x1c€]
R6KUL\x012€€€i€€€auth
---

keyfs man page says that #r/nvram holds keys too, how does one clear
that?

Any ideas?

-ishwar




                 reply	other threads:[~2001-06-05 16:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.30.0106051222580.24166-100000@pali.cps.cmich.edu \
    --to=ishwar@pali.cps.cmich.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).