From: Andrew <afrayedknot@thefrayedknot.armory.com>
To: 9fans@cse.psu.edu
Subject: [9fans] slow cpu server
Date: Wed, 23 Apr 2003 21:55:19 -0700 [thread overview]
Message-ID: <20030424045519.GA24464@thefrayedknot.armory.com> (raw)
So Ive been trying to get my plan9 network going with fossil. Ive followed
the instructions in the wiki. I have a cpu server, running fossil, and
mounting itself on bootup, i'll call it 'B'. Theres also an auth server
('A'), which now mounts its root from the fossil server. Everything
seems to be coming together nicely, except for the cpu server ('B'),
takes a _really_ long time to authenticate when i try to telnet to it,
it comes right back asking for a user, then pauses for a few minutes
before it prompts for a challenge/response. Any ideas? Thanks.
Andrew
next reply other threads:[~2003-04-24 4:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 4:55 Andrew [this message]
2003-04-24 7:36 ` Charles Forsyth
2003-04-24 15:41 ` Dan Cross
2003-04-24 15:49 ` Dan Cross
2003-04-24 18:10 ` Andrew
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=20030424045519.GA24464@thefrayedknot.armory.com \
--to=afrayedknot@thefrayedknot.armory.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).