From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] slow cpu server
Date: Thu, 24 Apr 2003 11:41:24 -0400 [thread overview]
Message-ID: <200304241541.h3OFfO503589@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 23 Apr 2003 21:55:19 PDT." <20030424045519.GA24464@thefrayedknot.armory.com>
> 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.
Sounds like a DNS issue. Are you using the long forms of hostnames?
e.g., auth.foo.com instead of auth? The former are looked up using
DNS, which can take a long time to timeout. The former are looked
up locally using /lib/ndb/*.
- Dan C.
next prev parent reply other threads:[~2003-04-24 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 4:55 Andrew
2003-04-24 7:36 ` Charles Forsyth
2003-04-24 15:41 ` Dan Cross [this message]
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=200304241541.h3OFfO503589@augusta.math.psu.edu \
--to=cross@math.psu.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).