From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] logout from cpu server
Date: Fri, 25 Jul 2003 20:37:31 -0400 [thread overview]
Message-ID: <e8df40c501ead83c7c493b79dd6bbd7c@plan9.bell-labs.com> (raw)
In-Reply-To: <20030725113833.R28024@cackle.proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 124 bytes --]
#c/key is replaced by factotum. If you want a getty-like program on the
console server, have it query factotum for logins.
[-- Attachment #2: Type: message/rfc822, Size: 3092 bytes --]
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] logout from cpu server
Date: Fri, 25 Jul 2003 11:38:36 +0200
Message-ID: <20030725113833.R28024@cackle.proxima.alt.za>
On Fri, Jul 25, 2003 at 06:12:25PM +0900, okamoto@granite.cias.osakafu-u.ac.jp wrote:
>
> peridotite# Ctl-d
> init: rc exit status: rc 106: false
> init: can't check password; insecure
>
That must be because:
if(consctl<0 || key<0 || write(consctl, "rawon", 5) != 5)
print("init: can't check password; insecure\n");
which could be due to a number of causes. Maybe we can check which of
consctl = open("#c/consctl", OWRITE);
key = open("#c/key", OREAD);
write(consctl, "rawon", 5);
is most likely to have failed. Hm, /dev/key (#c/key) doesn't seem to
exist anymore. Any suggestions from Bell Labs?
++L
next prev parent reply other threads:[~2003-07-26 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 8:02 okamoto
2003-07-25 8:19 ` C H Forsyth
2003-07-25 8:20 ` okamoto
2003-07-25 8:24 ` Charles Forsyth
2003-07-25 8:31 ` Lucio De Re
2003-07-25 9:12 ` okamoto
2003-07-25 9:38 ` Lucio De Re
2003-07-26 0:37 ` David Presotto [this message]
2003-07-26 3:29 ` boyd, rounin
2003-07-25 8:26 ` Fco.J.Ballesteros
2003-07-25 8:30 ` okamoto
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=e8df40c501ead83c7c493b79dd6bbd7c@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).