From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Standalone cpu/auth server..
Date: Thu, 19 Dec 2002 22:34:32 -0500 [thread overview]
Message-ID: <167b5034e4f9809f8abadaef73773b69@plan9.bell-labs.com> (raw)
I have no idea what's going on.
I think you're on your own for debugging it.
Things to try include using netkey auth
with the Plan 9 cpu command and reading
the log on the auth server for activity.
Russ
next reply other threads:[~2002-12-20 3:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 3:34 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-20 2:32 Russ Cox
2002-12-20 2:34 ` Ish Rattan
2002-12-20 1:18 Russ Cox
2002-12-20 2:23 ` Ish Rattan
2002-12-19 19:21 Ish Rattan
2002-05-07 19:19 rsc
2002-05-07 19:14 rsc
2002-05-07 17:49 Ish Rattan
2002-05-08 9:03 ` Don
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=167b5034e4f9809f8abadaef73773b69@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).